Migrate remaining secrets to ExternalSecrets #67
1 changed files with 7 additions and 4 deletions
Fix argocd SSH key format for 1Password Connect
1Password Connect doesn't support ?ssh-format=openssh, so we need a separate Secure Note item with the OpenSSH-formatted key. Created new 1Password item: argocd-forge-ssh-key Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
commit
8f4660915d
|
|
@ -2,8 +2,11 @@
|
|||
#
|
||||
# Replaces the manual op inject workflow from repo-forge-secret.yaml.tpl
|
||||
#
|
||||
# 1Password item: "argocd forge key" in blumeops vault
|
||||
# Field: "private key"
|
||||
# 1Password item: "argocd-forge-ssh-key" in blumeops vault (Secure Note)
|
||||
# Field: "private-key-openssh"
|
||||
#
|
||||
# Note: Uses a separate Secure Note item because 1Password Connect doesn't
|
||||
# support the ?ssh-format=openssh query parameter that the CLI uses.
|
||||
#
|
||||
# This is a repo-creds (credential template) that matches ALL repos under eblume/
|
||||
#
|
||||
|
|
@ -32,5 +35,5 @@ spec:
|
|||
data:
|
||||
- secretKey: privateKey
|
||||
remoteRef:
|
||||
key: argocd forge key
|
||||
property: private key
|
||||
key: argocd-forge-ssh-key
|
||||
property: private-key-openssh
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue