Jeff Mitchell
a6cca576a3
* Attempt canceling sessions by the client In some circumstances (like a Ctrl-C), the client knows it's shutting down and the TOFU token will be lost. In this case it makes sense to cancel the session rather than have it time out. This introduces a command enum to the handshake message which can be used for the client to send commands to the worker -- in this case the only specified command is to cancel the session. It doesn't occur if the session is already timed out or if we can't authorize connections as this generally means the session is already invalid.
5.5 KiB
5.5 KiB
Boundary CHANGELOG
Canonical reference for changes, improvements, and bugfixes for Boundary.
vNext
Changes/Deprecations
- controller: Switch the session connection limit for dev mode and the initial
target when doing database initialization to
-1. This makes it easier for people to start understanding Boundary while not hitting issues related to some programs/protocols needing multiple connections as they may not be easy for new users to understand. (PR)
New and Improved
- controller, worker, cli: When the client quits before the session time is over, but in a manner where the TOFU token will be locked, attempt canceling the session rather than leaving it open to time out (PR)
- controller: Improved error handling in hosts, host catalog and host set (PR)
- controller: Relax account login name constraints to allow dash as valid character (Issue) (PR)
- cli/connect/http: Pass endpoint address through to allow setting TLS server name directly in most cases (PR)
- cli/connect/kube: New
kubesubcommand forboundary connectthat makes it easy to routekubectlcommands through Boundary, including when usingkubectl proxy(PR)
Bug Fixes
v0.1.2
New and Improved
- docker: Official Docker image for
hashicorp/boundary(PR) - controller: Add ability to set public address for cluster purposes (Issue) (PR)
- ui: Improve scope awareness and navigation, including IAM for global scope (PR)
- ui: Add dark mode toggle (Issue) (PR)
- ui: Add scope grants to roles (PR)
- ui: Add IAM resources to global scope (PR)
Bug Fixes
- controller, worker: Fix IPv4-only check so
0.0.0.0specified without a port only listens on IPv4 (PR) - ui: Fix grant string corruption on updates (Issue) (PR)
- controller, cli: Fix mutual exclusivity bug with using -authz-token on
boundary connect(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.