Backport of Vault documentation: added known issues to 1.10.x upgrade guide into release/1.10.x #14689
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
hc-github-team-secure-vault-core
force-pushed
the
backport/update-upgrade-1-10-guide/exactly-premium-skunk
branch
from
53e99c1
to
32d7f9f
Compare
VioletHynes
added
the
hashicorp-contributed-pr
schavis
approved these changes
Aug 16, 2023
…/exactly-premium-skunk
ncabatoff
deleted the
backport/update-upgrade-1-10-guide/exactly-premium-skunk
branch
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.
Backport
This PR is auto-generated from #14685 to be assessed for backporting due to the inclusion of the label backport/website.
The below text is copied from the body of the original PR.
Per Aarti and Meggie, known issues were added to the upgrade guide for 1.10.x.
Since the known issues come from the release notes v.1.10.0, Meggie wanted to use the #@include directive so in case updates need to be made to known issues, the updates can be automatically propagated without having to access multiple files to make the updates. I'll need to figure out how to do this in the future.
🔍 Deploy Preview