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 introduces the handling logic for deprecated builtins as outlined in RFC VLT-200. The deprecation statuses are handled as follows:
VAULT_ALLOW_PENDING_REMOVAL_MOUNTS
is unsetThis logic has two net effects:
PendingRemoval
orRemoved
mount, the core will log Errors, seal itself, and shutdown immediately.PendingRemoval
orRemoved
Deprecation Status, the Vault server will return an error and disallow the mount.The
PendingRemoval
functionality described above may be overridden using theVAULT_ALLOW_PENDING_REMOVAL_MOUNTS
environment variable upon Vault server startup. This causes the mounts to behave as if they areDeprecated
, with a log level ofError
instead ofWarn
.