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

feat: save public key or its ID to secretFileData #76

Merged

Conversation

alxndr13
Copy link
Collaborator

@alxndr13 alxndr13 commented Feb 6, 2024

In our Project where we use skipper, we want to implement a feature where re-encryption of secrets is possible using a single command.

In our best-case scenario, we want to be able to replace the key in the inventory and let our project's CLI do the rest. But this means we have to know which was the OLD key and which is the NEW one, we want to re-encrypt our secrets with.

This change saves the "Public Key" (there's no such driver as of this PR, which uses a public key) or a Key Identifier (azurekv) to enable skipper to know which secret got encrypted with which key.

@alxndr13 alxndr13 requested a review from lukasjarosch February 6, 2024 12:36
@alxndr13 alxndr13 changed the title feat: save public key or its ID to secretData feat: save public key or its ID to secretFileData Feb 6, 2024
@alxndr13 alxndr13 force-pushed the feat-add-public-key-to-secrets branch from 91eb5ce to 60ef55d Compare February 8, 2024 10:36
secret/driver/azure.go Outdated Show resolved Hide resolved
secret/driver/plain.go Outdated Show resolved Hide resolved
@alxndr13 alxndr13 force-pushed the feat-add-public-key-to-secrets branch from 60ef55d to 0983873 Compare February 14, 2024 08:34
@alxndr13
Copy link
Collaborator Author

@lukasjarosch PR is now ready, PTAL.

@lukasjarosch lukasjarosch merged commit 2f376c7 into lukasjarosch:main Feb 14, 2024
9 checks passed
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.

2 participants