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

Decide (and document) what it should do on delete #13

Open
plumdog opened this issue Feb 28, 2020 · 2 comments
Open

Decide (and document) what it should do on delete #13

plumdog opened this issue Feb 28, 2020 · 2 comments

Comments

@plumdog
Copy link
Contributor

plumdog commented Feb 28, 2020

Currently, on delete does nothing to the secret if it was passed in. That is, the custom resource makes no attempt to remove the secret values that it put into the secret from the secret.

This feels like slightly surprising behaviour, but so does removing values from the secret which may have been manually altered since creation - not usually a concern of Cloudformation things, but somewhat uniquely so in the case of SecretsManager.

@plumdog
Copy link
Contributor Author

plumdog commented Nov 26, 2020

I think the answer here is that, by default, it should leave the value in the secret, but that it should be controllable with a switch.

@plumdog
Copy link
Contributor Author

plumdog commented Jan 18, 2021

Additional consideration: on update, it still calls putSecretValue, so if this merges with whatever is already in the secret, then doing nothing on delete would sort of make sense. If however, this is a straight "make the secret contain this and only this", then it should empty the secret on delete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant