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

VDS: remediate deleted destination secret #532

Merged
merged 1 commit into from
Dec 21, 2023

Conversation

benashz
Copy link
Collaborator

@benashz benashz commented Dec 21, 2023

Previously, the VDS controller did not detect when the destination secret had been deleted after it had initially created it.

Fixes:

  • ensure a deleted destination secret that is owned by the VDS controller results in a re-sync.
  • add integration test to test this use-case
  • update all other controller integration tests to test for destination deletion

Closes #228

Previously, the VDS controller did not detect when the destination
secret had been deleted after it had initially created it.

Fixes:
- ensure a deleted destination secret that is owned by the VDS
  controller results in a re-sync.
- add integration test to test this use-case
- update all other controller integration tests to test for destination
  deletion
@benashz benashz requested a review from a team as a code owner December 21, 2023 15:46
@benashz benashz added this to the v0.4.3 milestone Dec 21, 2023
@benashz benashz requested a review from kschoche December 21, 2023 15:50
Copy link
Contributor

@kschoche kschoche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@benashz benashz merged commit 8a8c259 into main Dec 21, 2023
40 checks passed
@benashz benashz deleted the VAULT-16730/vds-resync-on-destination-deletion branch December 21, 2023 22:15
adrianmoisey pushed a commit to adrianmoisey/vault-secrets-operator that referenced this pull request Jan 16, 2024
Previously, the VDS controller did not detect when the destination
secret had been deleted after it had initially created it.

Fixes:
- ensure a deleted destination secret that is owned by the VDS
  controller results in a re-sync.
- add integration test to test this use-case
- update all other controller integration tests to test for destination
  deletion
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.

operator doesn't refresh a deleted result secret if lease still within window
2 participants