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

[FEATURE] List of gpg keys to encryt secrets for #103

Open
muchgitsuchwow opened this issue Mar 9, 2022 · 1 comment · May be fixed by #297
Open

[FEATURE] List of gpg keys to encryt secrets for #103

muchgitsuchwow opened this issue Mar 9, 2022 · 1 comment · May be fixed by #297
Assignees
Labels
enhancement New feature or request

Comments

@muchgitsuchwow
Copy link

Might not be the usual case, for me it is.

Is your feature request related to a problem? Please describe.
I've strictly separated users for private and work. I've different gpg keyrings. Different private keys. Currently I can encrypt secrets for one key, which means I cannot use secrets in the same repository on other hosts with different keyrings.

Describe the solution you'd like
I hope it would be easily managable to add gpg_user_ids in addition to gpg_user_id as a list of gpg keys to encrypt data for.

Describe alternatives you've considered
Third-party like git crypt and bypass bombadil secrets management, I guess.

@muchgitsuchwow muchgitsuchwow added the enhancement New feature or request label Mar 9, 2022
@oknozor
Copy link
Owner

oknozor commented Mar 9, 2022

This is unsual indeed, I will try to implement this and we shall see.

@ibotty ibotty mentioned this issue May 2, 2023
@ibotty ibotty linked a pull request Oct 25, 2024 that will close this issue
ibotty added a commit to ibotty/toml-bombadil that referenced this issue Oct 25, 2024
This uses the key `gpg_user_ids`, but keeps `gpg_user_id` as alias for
backwards compatibility.

Fixes oknozor#103.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants