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

docs: Update release notes #5574

Merged
merged 4 commits into from
Mar 4, 2025
+35 −0
Merged

docs: Update release notes #5574

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e45ab97
docs: Update release notes
Dan-Heath Mar 3, 2025
7ae528d
docs: Clarify support in DHC topic
Dan-Heath Mar 4, 2025
bb27ebe
docs: Rewrite known issue for accuracy
Dan-Heath Mar 4, 2025
4b0a2c3
docs: Punctuation fix
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 Machine Scale Sets in both Flexible and Uniform orchestration modes.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't want folks to think we only support VMSS.

The Azure plugin supports Azure Virtual Machines, and Azure Virtual Machine Scale Sets in both Flexible and Uniform orchestration modes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point, thank you! I updated this line.

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'}}>
Deleted auth tokens prevent reauthentication
</td>
<td style={{verticalAlign: 'middle'}}>
In previous versions, when the auth tokens associated with a user were deleted, Boundary deleted the user as well. When the user logged in later, Boundary would have to reload the user's resources before they could access them.
<br/><br />
Version 0.19.1 introduces a soft delete for when a cached user's auth tokens are deleted and there is a valid refresh token that is less than 20 days old. Boundary marks the user as deleted, so they do not show up in lists and searches. But it keeps their user information in the cache.
<br /><br />
When the user logs in again, Boundary changes the user's status to active and there is no need to reload the resources. When the refresh token is older than 20 days, Boundary deletes the user and their resources from the cache.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there's some rewording needed here for accuracy?

Version 0.19.0 introduced the concept of a "soft delete" in the client cache, but there was an issue where "soft deleted" users weren't being restored when the user logs back in again. Version 0.19.1 addresses that issue. This was causing search functionality to break.

cc: @johanbrandhorst

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @moduli ! I reread the comments on #5549, and I think you are correct. I just pushed an updated version of this entry.

</td>
</tr>

</tbody>
</table>
Loading