✨ feat(VSecM Safe): #460 Manual Root Key Updates K8s Secret #725
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.
Manual Root Key Updates K8s Secret
Description
VSECM_MANUAL_ROOT_KEY_UPDATES_K8S_SECRET env variable added for giving an option to updating internal k8s secrets when manual root key provided.
Changes
app/safe/internal/privates.go
toapp/safe/internal/bootstrap/persist.go
since we use this function in theapp/safe/internal/server/route/receive.go
to persist keys with the manual root key. Therefore, it's not private tobootstrap
anymore.VSECM_MANUAL_ROOT_KEY_UPDATES_K8S_SECRET
tocore/safe.go
with its unit tests.VSECM_MANUAL_ROOT_KEY_UPDATES_K8S_SECRET
information details to docs/_pages/0110-configuration.md fileTest Policy Compliance
Code Quality
to understand.
Documentation
Checklist
Before you submit this PR, please make sure:
especially the test policy.
under the project’s license.
By submitting this pull request, you confirm that my contribution is made under
the terms of the project’s license and that you have the authority to grant
these rights.
Thank you for your contribution to VMware Secrets Manager
🐢⚡️!