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.

Sign up for GitHub

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

Jump to bottom

Persist orphan secrets #24

Open
abenabid opened this issue Aug 24, 2021 · 5 comments
Open

Persist orphan secrets #24

abenabid opened this issue Aug 24, 2021 · 5 comments
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request good first issue An issue that will be a good candidate for a new contributor priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@abenabid
Copy link

Describe the problem/challenge you have
Hello,

I've starting trying this tool today and it serves our need to synchronize secrets between namespaces.
But if we accidently delete the source secret, all the replicated secret will be deleted too.

Describe the solution you'd like
It would be nice to have a field in either SecretExport or SecretImport (preferably) which indicate to the controller to keep or delete the generated Secret on original Secret deletion.

Anything else you would like to add:
No

Best regards.
@abenabid abenabid added carvel-triage This issue has not yet been reviewed for validity enhancement This issue is a feature request labels Aug 24, 2021
@cppforlife
Copy link
Contributor

hey @abenabid 👋.

It would be nice to have a field in either SecretExport or SecretImport (preferably) which indicate to the controller to keep or delete the generated Secret on original Secret deletion.

yeah i think this could be a good addition for SecretImport.

@cppforlife cppforlife added carvel-accepted This issue should be considered for future work and that the triage process has been completed and removed carvel-triage This issue has not yet been reviewed for validity labels Aug 27, 2021
@abenabid
Copy link
Author

Hello @cppforlife,

Thank you for taking this idea into consideration.

Best regards

@joe-kimmel-vmw joe-kimmel-vmw added the good first issue An issue that will be a good candidate for a new contributor label Oct 11, 2021
@vrabbi
Copy link

vrabbi commented Jun 28, 2022

any plans on implementing this? this would be extremely useful for us in a few different use cases

@cppforlife
Copy link
Contributor

@vrabbi can you elaborate on what your use cases are for this feature?

@neil-hickey
Copy link
Contributor

This is still something we would consider, but some extra use-cases would be helpful indeed.

@neil-hickey neil-hickey added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request good first issue An issue that will be a good candidate for a new contributor priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Carvel
Status: Unprioritized
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cppforlife @neil-hickey @vrabbi @abenabid @joe-kimmel-vmw