Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of docs: Update release notes into stable-website #5575

Merged
merged 4 commits into from
Mar 4, 2025
Merged

Backport of docs: Update release notes into stable-website #5575

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ef0c2f4
backport of commit e45ab9715dc1fa94f2cf924e53be35c724d8e056
Dan-Heath Mar 3, 2025
8547804
backport of commit 7ae528d71f7c6c803feacdb55fa2c3284325b1c8
Dan-Heath Mar 4, 2025
856203e
backport of commit bb27ebe6095519061353c3c2fc6509da8203257f
Dan-Heath Mar 4, 2025
9de1201
backport of commit 4b0a2c30b72545fc2bf74d8efc2c716beb9551f8
Dan-Heath Mar 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions website/content/docs/concepts/host-discovery/azure.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ description: >-
# Azure dynamic host catalogs
Boundary uses dynamic host catalogs to automatically discover Azure resources available through Azure Resource Manager (ARM) and add them as hosts.

The Azure plugin supports Azure Virtual Machines and Azure Virtual Machine Scale Sets in both Flexible and Uniform orchestration modes.
It automatically discovers any individual virtual machines included in the scale sets and adds them as hosts.

## Create a host catalog to connect with Azure
Boundary uses plugins to integrate with a variety of providers. To use a
dynamic host catalog to integrate with Azure, you create a host catalog of the
Expand Down
32 changes: 32 additions & 0 deletions website/content/docs/release-notes/v0_19_0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,20 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
Azure Virtual Machine Scale Set support for dynamic host catalogs
</td>
<td style={{verticalAlign: 'middle'}}>
GA in version 0.19.1
</td>
<td style={{verticalAlign: 'middle'}}>
The Azure plugin now supports Azure Virtual Machine Scale Sets in both Flexible and Uniform orchestration modes for dynamic host catalogs. It automatically discovers any individual virtual machine instances that are part of the scale sets and adds them as hosts.
<br /><br />
Learn more:&nbsp;<a href="/boundary/docs/concepts/host-discovery/azure">Azure dynamic host catalogs</a>.
</td>
</tr>

</tbody>
</table>

Expand Down Expand Up @@ -199,5 +213,23 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
0.19.0
<br /><br />
(Fixed in 0.19.1)
</td>
<td style={{verticalAlign: 'middle'}}>
Soft-deleted users are not properly authenticated
</td>
<td style={{verticalAlign: 'middle'}}>
Version 0.19.0 introduced a soft delete for when a cached user's auth tokens are deleted, but there is a valid refresh token that is less than 20 days old. Boundary considers those users as deleted. But it keeps their user information in the cache so that it can restore the information, if they log in again.
<br /><br />
However, soft-deleted users were not being properly restored when they logged back in and it affected search capabilities.
<br/><br />
This issue is resolved in version 0.19.1. Soft-deleted users are now properly restored as active when they log in again if the refresh token is less than 20 days old.
</td>
</tr>

</tbody>
</table>
Loading