I have a project that needs commits to be signed with my gpg key. The commits are signed and argocd recognizes them as signed correctly, but it will not sync; saying "ComparisonError: Target revision ABC123 in Git is not signed, but a signature is required".
To Reproduce
Create a project setting spec.signatureKeys:
signatureKeys:
- keyID: 0F5C56E6213A7610
Assign the project to any application
Add the gpg public keys to argoCD
I use a gpg key with subkeys, but the master key is the one used to sign off commits:
Checklist:
argocd version
.Describe the bug
I have a project that needs commits to be signed with my gpg key. The commits are signed and argocd recognizes them as signed correctly, but it will not sync; saying "ComparisonError: Target revision ABC123 in Git is not signed, but a signature is required".
To Reproduce
spec.signatureKeys
:I use a gpg key with subkeys, but the master key is the one used to sign off commits:
When checking the commit in the command line, I see it is signed of correctly:
Also checking the gpg keyring on the argocd-repo-server, I see that my public key is there:
Expected behavior
ArgoCD should sync commits that are signed with the correct signatures.
Screenshots
Version
Logs