Use Event Notifications to Update VaultDynamicSecrets Instantly #1159
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.
Description
This PR updates VaultDynamicSecrets in VSO when the corresponding secret in Vault has a relevant event occur on it.
Manual Testing
This PR was manually validated against the Azure Secrets Enterprise engine using both static and dynamic role configurations. Although event notifications have not yet been implemented across all secrets engines, the changes in this PR are forward-compatible: each plugin exposes the same generic event types (creds-create, static-creds-create, rotate). Once the remaining plugins add support for these notifications, VSO builds that include this PR will automatically work with them without requiring further modifications.
Setup Azure Configuration and K8s Authentication with Vault
Create VaultDynamicSecret CRD for static and dynamic secret
Get Original Credential details for dynamic role
Confirmed that client secret was different after new lease generated
Setup original dyanmic secret for static role and see original creds
Confirmed that the client secret was updated on an instant basis after rotating the secret