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
{{ message }}
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
With the helm wrapper you can easily run "helm secrets install/upgrade/rollback" with secrets files included as -f option from you helm_vars values dir tree.
However, if you try to run something like helm secrets rollback releasename revision you (rightly) have it fail. Looking at this it looks like this was never implemented? When rolling back it doesn't seem like it does need to decrypt the files and such and re-encrypt them, that said I propose:
To support this option in the wrapper anyway. This will make usage of it more consistent.
To update the documentation with more specific details on how this works.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the docs it's specified that:
However, if you try to run something like
helm secrets rollback releasename revision
you (rightly) have it fail. Looking at this it looks like this was never implemented? When rolling back it doesn't seem like it does need to decrypt the files and such and re-encrypt them, that said I propose:To support this option in the wrapper anyway. This will make usage of it more consistent.
To update the documentation with more specific details on how this works.
The text was updated successfully, but these errors were encountered: