-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
context cannot be flushed and reencrypted anymore #175
Comments
Since I couldn't find a total obvious bug in the transcrypt skript to raise a PR, our current workaround is:
|
Hi @timmalich I have checked the I have a potential fix on the branch fix-flush-of-context, could you try this and confirm whether it fixes the flush problem for you? As a side note, given the process you describe you should try using the transcrypt --context=local --rekey --password=NewPassword --yes |
Hi @jmurty thanks for the amazing fast fix and sorry for the late reply. I can confirm that it works. Ignoring my limited knowledge on that matter: I would say that the code looks also good and readable to me. <3 |
Hi @timmalich thanks for confirming the fix, I have now merged it into the |
We have defined this context:
transcrypt -C local -c aes-256-cbc -p 'XXXXXXXXX'
Our gitattributes look like this:
kubernetes//secrets/ filter=crypt diff=crypt merge=crypt
kubernetes//local//secrets/** filter=crypt-local diff=crypt-local merge=crypt-local
kubernetes/**/secret-values.yaml filter=crypt diff=crypt merge=crypt
The files have already been reencrypted with XXXXXXXXX.
Now we would like to reencrypt the files in the local context yet again, but after running:
transcrypt -C local -f -F -y; transcrypt -C local --display
We still get:
Therefore, after running:
We get:
The text was updated successfully, but these errors were encountered: