-
Notifications
You must be signed in to change notification settings - Fork 899
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
Cannot output empty yaml file since sops-v3.7.0 #907
Comments
This looks caused for here: https://github.com/mozilla/sops/blob/v3.7.1/stores/yaml/store.go#L364 |
Switching back this behaviour will be super useful for my application of sops, thanks! |
@jarrettprosser would you mind describing what you need this behavior for? (@ikedam you as well maybe?) Please also see my comment: #791 (comment). |
@felixfontein sure thing. I'm not using sops directly, but it's part of a toolchain which broke when this change came into v3.7.0. We deploy resources to Kubernetes clusters using ArgoCD. In the git repos that represent resources, we use helm secrets to encrypt sensitive values so they aren't committed in plaintext. Helm secrets uses sops under the hood to encrypt yaml files. In order for ArgoCD to render the secret files, we need to include helm secrets as a custom tool. We configure the ArgoCD applications to use a custom tool called helm3-secrets which uses Sometimes, the deployment doesn't actually have sensitive values. Previously, we could have a secrets file with no content, encrypted by sops, as a placeholder so that the template command would run correctly. When sops 3.7.0 was released and we updated our ArgoCD, we found deployments with these placeholder files would fail to render with the |
I have application servers configured with yaml.
|
IMO:
|
sops-3.6.1
sops-3.7.1 (same to sops-3.7.0)
Encoded outputs are same for both versions:
sops-v3.6.1
sops-v3.7.1
The text was updated successfully, but these errors were encountered: