Jeff Mitchell
f063b8601c
We have behavior that causes "0.0.0.0" to only listen on IPv4, however, it also assumed there was a port suffixed. This changes it so that it also works with a port-less address.
2.8 KiB
2.8 KiB
Boundary CHANGELOG
Canonical reference for changes, improvements, and bugfixes for Boundary.
vNext
Bug Fixes
- controller, worker: Fix IPv4-only check so
0.0.0.0specified without a port only listens on IPv4 (PR)
v0.1.1
Changes/Deprecations
Note: in addition to changes marked below in this section, be aware that currently names of resources are case-sensitive, but in a future update they will become case-preserving but case-insensitive for comparisons (e.g. if using them to access targets).
- cli: There are two changes to token storage handling:
- Specifying
nonefor the-token-nameparameter has been deprecated in favor of specifyingnonefor the new-keyring-typeparameter. passis now the default keyring type on non-Windows/non-macOS platforms. See the CLI docs page for more information.
- Specifying
New and Improved
- cli: New
-keyring-typeoption andpasskeyring type for token storage (Issue) (PR) - connect: Allow using
-target-namein conjunction with either-target-scope-idor-target-scope-nameto connect to targets, rather than the target's ID (PR) - controller: Allow API/Cluster listeners to be Unix domain sockets (Issue) (PR)
- ui: Allow creating and assigning a host to a host set directly from the host set view (Issue) (PR)
Bug Fixes
- cli: Fix database init when locale isn't English (Issue) (PR)
- cli: Fix hyphenation in help output for resources with compound names (Issue) (PR)
- controller: Allow connecting to Postgres when using remote Docker in dev mode (Issue (PR)
- controller, worker: Fix listening on IPv6 addresses (Issue) (PR)
- worker: Fix setting controller address for worker in dev mode (Issue) (PR)
v0.1.0
v0.1.0 is the first release of Boundary. As a result there are no changes, improvements, or bugfixes from past versions.