You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I think that with the recent updates (4.0.0), the redesign of [secrets] in vars, there is no need to support different keys. I can easily manage different keys on different machines for different data in secrets, related to vars, bound to profiles, .. So bombadil effectively already supports this.
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 togpg_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.
The text was updated successfully, but these errors were encountered: