Backport of docs/ad: adds deprecation announcements and migration guide into release/1.13.x #19405
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
requested a review
from yhyakuna
as a code owner
hc-github-team-secure-vault-core
force-pushed
the
backport/docs/deprecate-ad/repeatedly-sharing-crappie
branch
2 times, most recently
from
6db372e
to
86ce870
Compare
austingebauer
approved these changes
Feb 28, 2023
austingebauer
deleted the
backport/docs/deprecate-ad/repeatedly-sharing-crappie
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 #19388 to be assessed for backporting due to the inclusion of the label backport/1.13.x.
The below text is copied from the body of the original PR.
This PR adds documentation to announce the deprecation of the Active Directory (AD) secrets engine in Vault 1.13. Additionally, it publishes a migration guide with steps to migrate to the LDAP secrets engine.
Note that the URL path didn't change when introducing a nested structure under Secrets Engines -> Active Directory. For that reason, I didn't include any redirects in this PR.
Related PR with changelog entry for this: #19334
馃攳 Deploy preview
Overview of commits