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
currently, the only way to track recipients is through comments.
while this works, if different profiles have different recipient sets, we'd need to duplicate the keys and comments for any shared recipients.
I'd like to suggest an option to define recipients, for example, as a table rather than an array of strings.
this way, recipients can be self-documented and optionally referenced in profiles if needed
to illustrate the idea:
[providers.age]
type = "age"
[providers.age.recipients]
admin = "key"alice = "key"bob = "key"github_ci = "key"
[profiles.staging.providers.age]
recipients_ref = ["alice", "bob"]
type = "age"
[profiles.production.providers.age]
recipients_ref = ["admin", "github_ci"]
type = "age"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey!
currently, the only way to track recipients is through comments.
while this works, if different profiles have different recipient sets, we'd need to duplicate the keys and comments for any shared recipients.
I'd like to suggest an option to define recipients, for example, as a table rather than an array of strings.
this way, recipients can be self-documented and optionally referenced in profiles if needed
to illustrate the idea:
Beta Was this translation helpful? Give feedback.
All reactions