only allow sops encryption of *.sops.* files #69
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate
waiting on upstream
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
CCCHH/ansible-infra!69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "only-encrypt-sops-files-with-sops"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This prevents users from accidentally encrypting any file with sops because only creation rules for e.g.
something.sops.yamlexist now. It also documents explicitly that all our sops files have this.sops.marker.7f80bb5e7ccafdb1aa30Running
sops editon a file (invalid or valid, just not existing yet), returns:cafdb1aa3099365d06b2@june wrote in #69 (comment):
ahh yes that was leftover from when I accidentally interpreted it as glob. should be fixed now
Ah, now I correctly can't create invalid files with sops, but also no valid ones either. Both error with:
99365d06b2a1891a9988@june wrote in #69 (comment):
this will now serve as my personal reminder to always quote YAML strings…
works now. for real for real.
Works now, very nice!!
a1891a99880788fde69d