You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ the secrets are stored in a Git repository and secured using SOPS.
35
35
#### Secret storage
36
36
37
37
Secrets are stored in any directory of your git repository. The GitOps CLI will pick
38
-
up any file that ends with `*.gitops.secret.enc.yml` or `*.gitops.secret.enc.yaml`. The secret files
39
-
must be encrypted using SOPS.
38
+
up any file that ends with `*.gitops.secret.enc.y[a]ml` except for `values.gitops.secret.enc.y[a]ml` (see [Secrets Templating](#secrets-templating))
39
+
The secret files must be encrypted using SOPS.
40
40
41
41
**NOTE:** Secrets MUST NEVER be committed into version control unencrypted.
42
42
Therefore, it is very much encouraged to add the following lines to your `.gitignore` file:
@@ -92,6 +92,12 @@ name: my-secret-name
92
92
93
93
This implies, that the filename must be a valid K8s secret name.
94
94
95
+
#### Secrets Templating
96
+
97
+
It is possible to use Go templates in the secret files. The values will originate from sops-encrypted `values.gitops.secret.enc.y[a]ml` files.
98
+
Values files can be located anywhere in the repository. The GitOps CLI will pick up all files that are located on the direct path towards the respective secret file.
99
+
Values files closer to the secret file will have higher precedence. Any object structure is allowed to be used in a values file.
0 commit comments