docs: update secret manager documentation #3534
Merged
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 explains the introduction of the
sm@
syntax introduced by #3411From its description:
We will introduce support for resolving values of the form
sm@secret_id
in addition to the already existingsm://secret_id
format. Users should move away fromsm://
and usesm@
instead. Usage ofsm://
will raise a warning about this being removed in the future. This has been tested usingspring-framework:6.2.2-SNAPSHOT
.The introduction of this syntax was suggested in a discussion of a regression caused by spring-framework:6.2.1 - see spring-projects/spring-framework#34124