Docs Changes for v0.8.0 (#2024)
* added new metrics doc * Minor format fixes * Use table to list metrics * Update website/content/docs/operations/index.mdx Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com> * fixed sentence * added worker proxy http * Update website/content/docs/operations/metrics.mdx Co-authored-by: Todd <github@quaddi.com> * Update based on the changes in draft * remove WIP note * Update website/content/docs/operations/metrics.mdx Co-authored-by: Todd <github@quaddi.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Todd <github@quaddi.com> * Update website/content/docs/operations/index.mdx Co-authored-by: Todd <github@quaddi.com> * Removed invalid metrics * Update header level * added code styling for "ops" listener and port 9203 description * added health endpoint document * resolved cherry-pick confict for 5edac3a7418f80e7d528f2fa7a461b1125c11806 * Incorporate review feedback * removed bad reference to metrics * added Other section for boundary_build_info * fixed typo * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Changed release notes structure Removed the empty "Releases" folder and now it goes straight to "Release Notes" * Update website/content/docs/operations/health.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Incorporate review feedback * Update website/content/docs/operations/index.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * added tutorial link * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update website/content/docs/operations/metrics.mdx Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * 0.8 Release Notes Added release notes page for 0.8 * corrected sensitive info redaction note * cleaned up visibility overview Co-authored-by: taoism4504 <loann@hashicorp.com> Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com> Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> Co-authored-by: Todd <github@quaddi.com> Co-authored-by: Timothy Messier <tim.messier@gmail.com> Co-authored-by: XingLu Wang <xinglu.wang@hashicorp.com> Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
This commit is contained in:
17 files changed
+365
-64
No files matched your search
@@ -0,0 +1,13 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Release Notes
|
||||
description: |-
|
||||
Boundary release notes
|
||||
---
|
||||
|
||||
# Release Notes
|
||||
|
||||
The side bar to the left has release notes for all major and minor releases of Boundary.
|
||||
|
||||
Downloads of Boundary can be found on the [Boundary Release Page](https://github.com/hashicorp/boundary/releases/)
|
||||
and the documentation is available on the [Boundary Changelog Page](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md).
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.1.0
|
||||
description: |-
|
||||
Boundary release notes for v0.1.0
|
||||
---
|
||||
|
||||
# [Boundary v0.1.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
v0.1.0 is the first release of Boundary. As a result there are no changes, improvements, or bugfixes from past versions. To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
## Boundary v0.1.0 Highlights
|
||||
|
||||
In this initial release, Boundary provides:
|
||||
|
||||
- Password-based authentication
|
||||
- Authenticated and authorized [TCP-based sessions](/docs/common-workflows/manage-sessions).
|
||||
- Identity and access management providing [role-based controls](/docs/common-workflows/manage-roles) for principals.
|
||||
- A user interface for administration of Boundary resources.
|
||||
- A [Terraform provider](https://github.com/hashicorp/terraform-provider-boundary) for managing Boundary resources.
|
||||
- A fully instrumented command line interface for managing Boundary and for establishing and managing sessions.
|
||||
- A fully instrumented [Boundary golang SDK](/docs/api-clients/go-sdk).
|
||||
- A log of Boundary sessions exposed through Boundary's administrator UI and postgres database.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.2.0
|
||||
description: |-
|
||||
Boundary release notes for v0.2.0
|
||||
---
|
||||
|
||||
# [Boundary v0.2.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about Boundary v0.2.0 as well as new features since Boundary's 0.1.0 that became available in 0.1.x releases. To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md). To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.2.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.2.0 Highlights
|
||||
|
||||
**Open ID Connect (OIDC) Authentication**: Boundary 0.2 adds support for OIDC authentication methods, which allow users to delegate authentication to an OIDC provider.
|
||||
This feature enables Boundary to integrate with popular identity providers like Microsoft Azure Active Directory, Okta,
|
||||
cloud identity management systems such as AWS IAM, and others. To get started with creating OIDC auth methods to log into Boundary with common OIDC providers,
|
||||
get started with the new [Boundary OIDC learn tutorial](https://learn.hashicorp.com/boundary).
|
||||
|
||||
**Boundary Desktop for MacOS:** Boundary Desktop enables users to use Boundary to access resources through a convenient GUI application. Boundary Desktop enables users to
|
||||
|
||||
- **Login with available auth methods**: Users can now login to Boundary Desktop with all support auth methods, including OIDC.
|
||||
- **Find targets:** Users can browse available targets.
|
||||
- **Connect to targets:** Users can connect to targets via Boundary Desktop.
|
||||
- **Manage sessions:** Users can manage all of their active sessions or drill down to sessions associated with a specific target.
|
||||
- **AutoUpdate:** AutoUpdate the Boundary Desktop app as new versions become available.
|
||||
|
||||
**Worker tags & filters (0.1.5):** Enable target traffic to be effectively “tied” to a given set of workers with [worker tags](https://www.boundaryproject.io/docs/concepts/filtering/worker-tags), forcing the session to occur through specified workers for a specific target.
|
||||
|
||||
Improvements to list actions:\*\* There have been numerous improvements to listing actions since Boundary 0.1.0.
|
||||
|
||||
- **Resource filtering (0.1.8):** allows users to navigate their resources more easily by [filtering list actions based on resource information](https://www.boundaryproject.io/docs/concepts/filtering/resource-listing).
|
||||
- **Recursive listing (0.1.5):** allows users to recursively list resources across a scope.
|
||||
- **List authorizations (0.1.5):** allows users to see what actions they’re authorized to perform against the resources returned in a list command.
|
||||
|
||||
**Database migrations (0.1.5):** Boundary provides an [easy upgrade path](https://learn.hashicorp.com/tutorials/boundary/upgrade-version) with fail-safes in the event of migration issues.
|
||||
This includes support for database upgrades in a single transaction.
|
||||
|
||||
## What's Changed
|
||||
|
||||
- **Authentication:** The auth-methods \{id}:authenticate:login action is deprecated and will be removed in a few releases. (Yes, this was meant to deprecate the authenticate action; apologies for going back on this!) To better support future auth methods, and especially the potential for plugins, rather than defining custom actions on the URL path the authenticate action will consume both a map of parameters but also a command parameter that specifies the type of command. This allows workflows that require multiple steps, such as OIDC, to not require custom subactions. Additionally, the credentials map in the authenticate action has been renamed attributes to better match other types of resources. credentials will still work for now but will be removed in a few releases. Finally, in the Go SDK, the Authenticate function now requires a command value to be passed in.
|
||||
- Related to the above change, the output of an API auth-methods \{id}:authenticate call will return the given command value and a map of attributes that depend on the given command. On the SDK side, the output of the Authenticate function returns a map, from which a concrete type can be easily umarshaled (see the updated authenticate password command for an example).
|
||||
|
||||
**For more detailed information of all changes since 0.1.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)**
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.3.0
|
||||
description: |-
|
||||
Boundary release notes for v0.3.0
|
||||
---
|
||||
|
||||
# [Boundary v0.3.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about Boundary v0.3.0, Boundary Desktop v1.1.0, as well as new features since Boundary's 0.2.0 that became available in 0.2.x releases. To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md). To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.3.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.3.0 Highlights
|
||||
|
||||
**Boundary Desktop for Windows:** [Boundary Desktop v1.1.0](https://releases.hashicorp.com/boundary-desktop/) gives users the ability to connect to remote targets and view active session details. Boundary Desktop is now available for both Windows and MacOS.
|
||||
|
||||
**Managed groups:** Managed groups allow the population of Boundary groups based on external IdP metadata. This feature allows users of our OIDC authentication method to automatically create groups based on the IdP they’re integrating with over OIDC.
|
||||
|
||||
**OIDC configuration improvements:** Administrators can now configure Boundary authentication from OIDC identity providers in the Boundary admin console and Boundary's Terraform Provider.
|
||||
|
||||
## What's Changed
|
||||
|
||||
For detailed information of all changes since 0.2.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.4.0
|
||||
description: |-
|
||||
Boundary release notes for v0.4.0
|
||||
---
|
||||
|
||||
# [Boundary v0.4.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about new functionality available in Boundary v0.4.0. To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md). To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.4.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.4.0 Highlights
|
||||
|
||||
**Session Credential Brokering:** Boundary 0.4, adds a Vault integration for the brokering of [Vault](https://www.vaultproject.io/) secrets to Boundary clients (both command line and desktop clients) for use
|
||||
in Boundary sessions. Brokering of Vault secrets is the foundation of Boundary’s larger credential-management story for seamless single sign-on to infrastructure targets. This feature introduces new Boundary resources - [credential stores](https://www.boundaryproject.io/docs/concepts/domain-model/credential-stores), [credential libraries](https://www.boundaryproject.io/docs/concepts/domain-model/credential-libraries), and [credentials](https://www.boundaryproject.io/docs/concepts/domain-model/credentials) -
|
||||
to support binding credentials with user sessions, as well as surfacing those credentials during session initialization on the command line and in Boundary Desktop.
|
||||
|
||||
**`boundary connect` Credential Brokering Integration:** Additionally, we have started integration into the [boundary connect helpers](https://www.boundaryproject.io/docs/getting-started/connect-to-target), starting in this release with the Postgres helper; if the credential contains a username/password and boundary connect postgres is the helper being used, the command will automatically pass the credentials to the psql process.
|
||||
|
||||
**Session Security Improvements:** Boundary workers will now close any existing proxy connections they're handling when they cannot make a status request to the worker. The timeout for this behavior is currenly 15 seconds.
|
||||
|
||||
## What's Changed
|
||||
|
||||
For more detailed information of all changes since 0.3.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.5.0
|
||||
description: |-
|
||||
Boundary release notes for v0.5.0
|
||||
---
|
||||
|
||||
# [Boundary v0.5.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about new functionality available in Boundary v0.5.0.
|
||||
To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md).
|
||||
To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.5.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.5.0 Highlights
|
||||
|
||||
**Event Logging:** 0.5.0 includes significant improvements to Boundary's event logging system with goal of giving operators greater visibility into system information in a well-defined, structured format.
|
||||
When enabled, event logs are the only type of logging Boundary performs, meaning standard system information and debug logs will no longer appear in stdout.
|
||||
The new structured event logs are filterable by event type and other expressions that users define. Legacy HCLog output is still supported through a user-configurable setting.
|
||||
|
||||
For more about event logging usage, see our [documentation](https://www.boundaryproject.io/docs/configuration/events/overview).
|
||||
|
||||
**Credential CRUD operations for Administrative Console:** The 0.5.0 release enables administration to configure Vault credential libraries and Vault credential set resources through the administrative console.
|
||||
Vault credential resources allows users to create Boundary sessions with credentials brokered by a Vault deployment.
|
||||
|
||||
## What's Changed
|
||||
|
||||
For more detailed information of all changes since 0.4.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.6.0
|
||||
description: |-
|
||||
Boundary release notes for v0.6.0
|
||||
---
|
||||
|
||||
# [Boundary v0.6.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about new functionality available in Boundary v0.6.0 and the corresponding Boundary Desktop v1.3.0 and Boundary Terraform Provider v1.0.5 releases.
|
||||
To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md).
|
||||
To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.6.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.6.0 Highlights
|
||||
|
||||
**Permissions-based UI:** Boundary 0.6.0 dynamically tailors the administrator console to individual users’ permissions, ensuring users are presented only with actions and workflows that can succeed.
|
||||
|
||||
**Linux Support for Boundary Desktop:** Boundary Desktop 1.3 adds support for Debian-based Linux distributions in addition to existing macOS and Windows support.
|
||||
|
||||
**Managed group configurations via Terraform:** Managed groups can now be configured via Terraform using v1.0.5 of [Boundary's Terraform Provider](https://registry.terraform.io/providers/hashicorp/boundary/latest)
|
||||
|
||||
## What's Changed
|
||||
|
||||
For more detailed information of all changes since 0.5.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.7.0
|
||||
description: |-
|
||||
Boundary release notes for v0.7.0
|
||||
---
|
||||
|
||||
# [Boundary v0.7.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about new functionality available in Boundary v0.7.0 and the corresponding Boundary Desktop v1.4.0 release.
|
||||
To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md).
|
||||
To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.7.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.7.0 Highlights
|
||||
|
||||
**Dynamic Host Catalogs:** Boundary introduces a new resource type, dynamic host catalogs, which automate the discovery of host resources from a catalog provider. The 0.7 release includes
|
||||
initial support for Azure and AWS host catalogs with more catalog providers to follow in future releases. Catalogs are implemented via Boundary's (currently internal) new go-plugin system.
|
||||
|
||||
**Managed group configuration in the admin console**: Managed groups are a special type of IAM group which populate users based on administrator-defined filters of external identity provider (IdP) metadata.
|
||||
Configuration of managed groups is now available in the Boundary admin console.
|
||||
|
||||
**UI Support for Resource Filtering:** Users may now filter auth method and session resources in the admin console and Boundary Desktop.
|
||||
|
||||
## What's Changed
|
||||
|
||||
For more detailed information of all changes since 0.6.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: v0.8.0
|
||||
description: |-
|
||||
Boundary release notes for v0.8.0
|
||||
---
|
||||
|
||||
# [Boundary v0.8.0](https://www.boundaryproject.io/downloads)
|
||||
|
||||
The release notes below contain information about new functionality available in the Boundary v0.8.0 release.
|
||||
To see a granular record of when each item was merged into the Boundary project, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md).
|
||||
To learn about what Boundary consists of, we highly recommend you start at the [Getting Started Page](/docs/getting-started).
|
||||
|
||||
Lastly, for instructions on how to upgrade an existing Boundary deployment to v0.8.0, please review Boundary’s [general upgrade guide](https://learn.hashicorp.com/tutorials/boundary/upgrade-version).
|
||||
|
||||
## Boundary v0.8.0 Highlights
|
||||
|
||||
**Metrics and Health Endpoint:** Boundary is adding [Prometheus metrics](https://www.boundaryproject.io/docs/operations/metrics) to monitor the operations of workers and controllers,
|
||||
as well as a [health endpoint](https://www.boundaryproject.io/docs/operations/health) for controllers.
|
||||
|
||||
**Audit Event Logs:** We are expanding the audit event logs by increasing the captured [audit events](https://www.boundaryproject.io/docs/configuration/events/overview),
|
||||
with support for sanitizing sensitive information from audit events. All of the events are now classified and events contain more usable data, with sensitive information redacted by default.
|
||||
|
||||
**UI Support for Worker Tags:** Users can now set and edit [worker tag](https://www.boundaryproject.io/docs/concepts/filtering/worker-tags) filters in the Boundary admin console.
|
||||
|
||||
**Performance Improvements:** We have implemented changes to improve performance on larger deployments; such as adding a refresh button in the admin console and desktop client,
|
||||
and improving response times listing sessions and targets. We plan to continue these efforts as Boundary users grow their deployments!
|
||||
|
||||
|
||||
## What's Changed
|
||||
|
||||
For more detailed information of all changes since 0.7.0, please refer to the [Changelog](https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md)
|
||||
|
||||
Reference in new issue
Block a user