* added boundary connect -target-name example
* removes some passive and ableist language
* Apply suggestions from code review
add rewrite suggestions from @hugoamvieira
Co-authored-by: Hugo <hugoamvieira@users.noreply.github.com>
* update Using Connect Helpers copy
Co-authored-by: Hugo <hugoamvieira@users.noreply.github.com>
* feat: display warning in IE 11
* Use innerHTML instead of manual DOM
Co-authored-by: Randall Morey <randall@hashicorp.com>
* link to HashiCorp IE11 deprecation page
Co-authored-by: Randall Morey <randall@hashicorp.com>
This feature allows the user to set the `controllers` field to a string
that points to either an environment variable or file.
We then dynamically pull out the value and parse it into the config.
This feature allows the user to set the `tags` field to a string
that points to either an environment variable or file.
We then dynamically pull out the value and parse it into the config.
This can also be done at the keys level, where you set your keys
directly in Boundary's config file, but point the values to env/file.
This stores worker connection nonces within the database to ensure
uniqueness of connections. Prior the connection required any attacker to
be able to decrypt the incoming encrypted authentication message in
order to replay (and if the attacker has access to the KMS you have
bigger problems), but with this change even if an attacker does have
access to the KMS key, they cannot reuse the same message. (If they're
able to encrypt against the KMS key, they can still act as a worker with
a new message, so this only really helps if they only have decryption
capabilities.)
* website: use canary release of open-api-page
* website: bump to latest open-api-page pre-release
* chore: bump to latest open-api-page pre-release
* chore: refresh package files from main to avoid conflicts
* bump to stable open-api-page release
This puts it more in line with other upcoming options that use "dir"
instead of "directory" (plus it's easier to type), and makes it clear
that this directory and the passthrough behavior is related to the UI as
opposed to other upcoming items.