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
Add new logic for looking up Strongbox Secrets (#112)
We now reverted to the original logic to always look up the Strongbox
Secret and "fail open" (skip decrypting) when we do not find it.
We are adding a safeguard, we now check `kustomize build` output for
Strongbox headers in Secret data and will fail if found.
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,8 @@ resources:
41
41
42
42
### Strongbox envvars
43
43
44
-
Secret name containing Strongbox keyring/identity file MUST be `argocd-voodoobox-strongbox-keyring`.
44
+
Secret name containing Strongbox keyring/identity file MUST be
45
+
`argocd-voodoobox-strongbox-keyring`.
45
46
46
47
Key name for keyring MUST be `.strongbox_keyring`
47
48
@@ -238,7 +239,6 @@ subjects:
238
239
- kind: ServiceAccount
239
240
name: argocd-repo-server
240
241
namespace: sys-argocd
241
-
242
242
```
243
243
244
244
### Plugin Configuration
@@ -258,7 +258,6 @@ subjects:
258
258
|-|-|-|
259
259
| ARGOCD_APP_NAME | set by argocd | name of application |
260
260
| ARGOCD_APP_NAMESPACE | set by argocd | application's destination namespace |
261
-
| STRONGBOX_ENABLED | "true" | Enable Strongbox for decryption |
262
261
| STRONGBOX_SECRET_NAMESPACE | | the name of a namespace where secret resource containing strongbox keyring is located, defaults to current |
263
262
| GIT_SSH_CUSTOM_KEY_ENABLED | "false" | Enable Git SSH building using custom (non global) key |
264
263
| GIT_SSH_SECRET_NAMESPACE | | the value should be the name of a namespace where secret resource containing ssh keys are located, defaults to current |
0 commit comments