Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Note on the name of the configuration file #1569

Merged
merged 2 commits into from
Aug 13, 2024
Merged

Note on the name of the configuration file #1569

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca66e3c
Note on the name of the configuration file
ErraticMaker Jul 30, 2024
2e03f83
Use ReST admonition syntax for note
ErraticMaker Jul 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -669,6 +669,11 @@ of all new files. If your secrets are stored under a specific directory, like a
``git`` repository, you can create a ``.sops.yaml`` configuration file at the root
directory to define which keys are used for which filename.

.. note::

The file needs to be named ``.sops.yaml``. Other names (i.e. ``.sops.yml``) won't be automatically
discovered by SOPS. You'll need to pass the ``--config .sops.yml`` option for it to be picked up.

Let's take an example:

* file named **something.dev.yaml** should use one set of KMS A, PGP and age
Expand Down
Loading