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.
When there are many secrets one has to add them one by one, which is not only inconvenient but also pollutes the GitHub workflow files.
Describe the solution you'd like
Allow importing secrets using regex/glob pattern. For example to specify secrets for the dev environment one could import secrets using the "DEV_*" pattern.
The text was updated successfully, but these errors were encountered:
Hi @rafiksargsyan - I want to confirm that you're asking for something like the following which builds on wildcard multiple secret support at the key-value level:
This seems like a reasonable request if that's the case. If you're asking to support many secrets at the Vault KV path level (for example, secret/data/ci/*), then I don't think it's something we can do with Vault today.
Is your feature request related to a problem? Please describe.
When there are many secrets one has to add them one by one, which is not only inconvenient but also pollutes the GitHub workflow files.
Describe the solution you'd like
Allow importing secrets using regex/glob pattern. For example to specify secrets for the dev environment one could import secrets using the "DEV_*" pattern.
The text was updated successfully, but these errors were encountered: