-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
connect/ca: require new vault mount points when updating the key type/bits for the vault connect CA provider #10331
Conversation
This is similar in spirit to #10330 |
1a6dedd
to
7feabba
Compare
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.
LGTM! This seems like it fixes the UX problem for the vault provider by refusing the update when it can't be fully applied. The error message should make it clear to the user how to resolve the issue.
…/bits for the vault connect CA provider progress on #9572
Co-authored-by: Daniel Nephin <[email protected]>
Co-authored-by: Daniel Nephin <[email protected]>
Co-authored-by: Daniel Nephin <[email protected]>
cfc4fba
to
5098e7b
Compare
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/408180. |
progress on #9572