From 8f4660915d4dbee51fbaf8bc3a34df1146dfb2bb Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Wed, 28 Jan 2026 20:31:16 -0800 Subject: [PATCH] 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 --- .../manifests/argocd/external-secret-repo-forge.yaml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/argocd/manifests/argocd/external-secret-repo-forge.yaml b/argocd/manifests/argocd/external-secret-repo-forge.yaml index 1f96a43..dbb6724 100644 --- a/argocd/manifests/argocd/external-secret-repo-forge.yaml +++ b/argocd/manifests/argocd/external-secret-repo-forge.yaml @@ -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