docs: Update release notes #5574
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benemon
reviewed
Mar 4, 2025
| @@ -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. | |||
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Great point, thank you! I updated this line.
moduli
reviewed
Mar 4, 2025
Comment on lines
226
to
230
| 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. |
There was a problem hiding this comment.
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
moduli
approved these changes
Mar 4, 2025
Dan-Heath
added
the
backport/website
stellarsquall
approved these changes
Mar 4, 2025
This was referenced Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the release notes:
Updates the Azure DHC topic to mention support for scale sets.