hashicorp/boundary v0.19.0

on GitHub

0.19.0 (2025/01/31)

New and Improved

• Introduces soft-delete for users within the client cache.
  (PR).

• GCP dynamic host catalog: Add dynamic host catalog support for
  discovering GCP Compute Engine VM Instances.
  (PR).

• The worker domain has been refactored to create clear domain functions for worker operations, improve readability and
  maintainability of worker queries, and improve DB performance. (PR).

• Adds support for dual-stack networking for AWS operations.
  (PR)

  • Note: As a consequence of updating AWS SDK dependencies to enable
    dual-stack support, this Boundary release may consume more memory. From our
    testing, the increase seems to be around 1.6x, however this
    may vary depending on your deployment architecture.

• The worker <-> controller communications have been refactored to improve performance
  and reliability at large scale. Workers older than v0.19.0 will remain supported
  until the release of v0.20.0, in accordance with
  our worker/controller compatiblity policy.

• Add concurrency limit on the password hashing of all password auth methods.
  (PR).

  This avoids bursty memory and CPU use during concurrent password auth method
  authentication attempts. The number of concurrent hashing operations
  can be set with the new concurrent_password_hash_workers configuration
  value in the controller stanza, or the new
  BOUNDARY_CONTROLLER_CONCURRENT_PASSWORD_HASH_WORKERS environment variable.
  The default limit is 1.

• ui: Improve worker filter workflow for targets, vault credential-stores, and storage-buckets. (PR).

Bug fixes

• Fix bug in applying BOUNDARY_MAX_RETRIES for boundary cli. Previously
  setting this environment variable would result in a max retries of 2,
  regardless of the value set.
  (PR).
• Fix bug in parsing IPv6 addresses. Previously setting a target address or the
  initial upstream address in the config file would result in a malformed value.
  (PR).
• Fix an issue where, when starting a session, the connection limit always displays 0.
  (PR).
• Fix bug which caused the children keyword not to apply the appropriate
  permissions for a number of resources.
  (PR).