Skip to content
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

Backport of Vault-4279 reporting redundant/unused keys in config into release/1.10.x #14829

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #14752 to be assessed for backporting due to the inclusion of the label backport/1.10.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


The Vault server does not warn about configurations that contain invalid configuration keys.

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/reject-redundant-unused-keys-in-config/normally-new-flamingo branch from a4e9ef1 to 9e20544 Compare April 1, 2022 14:35
@vercel vercel bot temporarily deployed to Preview – vault April 1, 2022 14:35 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook April 1, 2022 14:49 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook April 1, 2022 16:42 Inactive
@hghaf099 hghaf099 merged commit 1f6cd70 into release/1.10.x Apr 1, 2022
@hghaf099 hghaf099 deleted the backport/reject-redundant-unused-keys-in-config/normally-new-flamingo branch April 1, 2022 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants