Open jeunii opened 2 years ago
@jeunii it’s because you are putting in plain text and using the data field. A couple different options.. base64 the cert in AWS, use the base64modifier or switch the data field to stringData in the yaml file.
@werne2j thanks for the reply. you mentioned
use the base64modifier
could you please elaborate on this ?
Sorry, meant to say base64encode modifier but the docs are here https://argocd-vault-plugin.readthedocs.io/en/stable/howitworks/#base64encode
@jeunii is this still an issue?
I had a similar issue and as indicated by @werne2j did a base64 encoding to my key in AWS Secret Manager along with changing yaml file to data instead of stringData and it all worked.
Only issue I found with base64 encoding was it still had newline characters which required to be removed before updating AWS SM. Maybe I need to apply some more flags during base64 encoding.
Describe the bug I am trying to create a
kubernetes.io/tls
type secret in my k8s cluster. My secret manifest looks likeIn AWS secret manager, under
dev/argocd
I have,But in ArgoCD when I try to sync the secret, I get the error message
All other types of secrets fetching works. but not when im trying to import certs/keys.
Is this a limitation of this plugin ?