4 ms·
If your only use case for Vault is access to K/V secrets during a workflow (CD for example) -- then sure, it's a much simpler alternative. If you need access to
by rileymichael 6y ago
If your only use case for Vault is access to K/V secrets during a workflow (CD for example) -- then sure, it's a much simpler alternative. If you need access to secrets dynamically / at runtime (outside of the Actions container), or any of the other features Vault has, then no.
- izolate 6y agoI’m not sure if you’re aware but the GitHub API provides dynamic access to the secrets so you can theoretically use it in your application/outside your workflow.
- rileymichael 6y agodo you happen to have a link to the api docs for that? Everywhere I'm looking it doesn't return the value. https://developer.github.com/v3/actions/secrets/#get-a-repository-secret https://developer.github.com/v3/actions/secrets/#get-a-repos... and the blog states the same behavior I'm seeing in the docs: First, the API doesn’t return any values, only names. https://github.blog/2020-02-06-manage-secrets-and-more-with-the-github-actions-api/#managing-secrets https://github.blog/2020-02-06-manage-secrets-and-more-with-...
- izolate 6y agoNo, you're right, I was mistaken. Sorry about that.