Skip to content
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.

"no matching creation rules found" for helm-secrets version 2.0.0 #92

Closed
max-rocket-internet opened this issue Jan 16, 2019 · 6 comments · Fixed by #117
Closed

"no matching creation rules found" for helm-secrets version 2.0.0 #92

max-rocket-internet opened this issue Jan 16, 2019 · 6 comments · Fixed by #117

Comments

@max-rocket-internet
Copy link

I run helm plugin update secrets and got version 2.0.0 earlier today.

This newer version produces this error where version 1.3.1 worked fine:

$ helm secrets enc kubernetes/charts/apps/xxx/values/xxx/secrets.yaml
Encrypting kubernetes/charts/apps/xxx/values/xxx/secrets.yaml
error loading config: no matching creation rules found
Error: plugin "secrets" exited with error

I noticed there is no 2.0.0 release on Github. What's the deal?

@dkoleary88
Copy link

Same issue here. Had to downgrade to v1.3.1.

@max-rocket-internet
Copy link
Author

The fix:

helm plugin remove secrets
helm plugin install --version 1.3.1 https://github.com/futuresimple/helm-secrets

@jonathancolby-olx
Copy link

jonathancolby-olx commented May 15, 2019

same here with version 2.0.1.

dir structure:

.
├── .sops.yaml
├── mysubdirectory
│   ├── secrets.yaml

.sops.yaml

---
creation_rules:
- path_regex: mysubdirectory/secrets.yaml
  kms: 'arn:aws:kms:eu-west-1:my-kms-key-redacted'

helm secrets dec mysubdirectory/secrets.yaml (works OK, mysubdirectory/secrets.yaml.dec created)

helm secrets enc  mysubdirectory/secrets.yaml
Encrypting mysubdirectory/secrets.yaml
error loading config: no matching creation rules found
Error: plugin "secrets" exited with error```

and original mysubdirectory/secrets.yaml is destroyed (emptied)

after downgrading to 1.3.1, above steps work correctly, and creation_rule in .sops.yaml is correctly found

@mateuszzawisza
Copy link
Contributor

Just merged #117 which seems to solve the issue. Please let me know if you experience any problems if using master.

@mhyllander
Copy link
Contributor

mhyllander commented Jun 24, 2019

@mateuszzawisza I think #117 may have caused a regression. See my reasoning in #121 (comment).

@mhyllander
Copy link
Contributor

There are some issues with sops path_regex:

getsops/sops#465
getsops/sops#480

The first issue was fixed in the latest sops 3.3.1. Using that sops version the creation rules above work for me without #117.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants