-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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.
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: add known issues section to 1.9.x upgrade guide #13662
Merged
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
fairclothjm
approved these changes
Jan 13, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @calvn !
tomhjp
reviewed
Jan 14, 2022
Co-authored-by: Tom Proctor <[email protected]>
tomhjp
approved these changes
Jan 19, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
fairclothjm
approved these changes
Jan 19, 2022
This was referenced Jan 19, 2022
calvn
added a commit
that referenced
this pull request
Jan 19, 2022
* docs: add known issues section to 1.9.x upgrade guide * minor rephrasing on oidc known issue * use relative references for URLs * Update website/content/docs/upgrading/upgrade-to-1.9.x.mdx Co-authored-by: Tom Proctor <[email protected]> * update known issues section for id token Co-authored-by: Tom Proctor <[email protected]>
calvn
added a commit
that referenced
this pull request
Jan 20, 2022
…o release/1.9.x (#13713) * no-op commit due to failed cherry-picking * [VAULT-3252] Add entity-alias behavior change to docs (#13370) * Add entity-alias behavior change to docs * Add upgrade note about entity-alias mapping change * Rename 1.7-9 upgrade pages, shuffle upgrade note position * Update website/content/partials/entity-alias-mapping.mdx Co-authored-by: Meggie <[email protected]> * Add incorrect policy issue to the docs * Add example about entity-alias restriction Co-authored-by: Meggie <[email protected]> * Update http requests API link to versioned docs (#13692) * docs: add known issues section to 1.9.x upgrade guide (#13662) * docs: add known issues section to 1.9.x upgrade guide * minor rephrasing on oidc known issue * use relative references for URLs * Update website/content/docs/upgrading/upgrade-to-1.9.x.mdx Co-authored-by: Tom Proctor <[email protected]> * update known issues section for id token Co-authored-by: Tom Proctor <[email protected]> Co-authored-by: temp <[email protected]> Co-authored-by: Pratyoy Mukhopadhyay <[email protected]> Co-authored-by: Meggie <[email protected]> Co-authored-by: Tony Pulickal <[email protected]> Co-authored-by: Calvin Leung Huang <[email protected]> Co-authored-by: Tom Proctor <[email protected]>
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.
Adds a "Known Issues" section to our 1.9.x upgrade guide, and includes a note about a panic that can be encountered on Vault installations that are using the ID token backend and have named keys created.