Skip to content

Sops cannot find config file if it's named .sops.yml (instead of .sops.yaml) #1567

@ErraticMaker

Description

@ErraticMaker

I don't know if it is a hard requirement that the sops config file is exactly .sops.yaml for it to be auto-discovered, or if it should accept the alternative .yml extension too, but it took me a while to realize this was the issue I was having.

So, it might be good to have a warning in the docs stating that it should match exactly to save some time to anyone facing the same issue. Or even better would be to allow the file to have either of those extensions.

I think the code where the name is defined to match that specific file name is here just for reference.

Thank you for the great work!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions