secrets for Amazon secrets manager ASM get double set of keys

[babadofar]

Somehow the updating of secrets in ASM never worked on my cluster due to missing permissions, Now the permissions were fixed and the secrets are botched.
The secrets now get an extra key, like this

oauth: {"oauth": "ghp_kkkke"}

while the expectation is that the secret should be like

{"oauth": "ghp_kkkke"}

[babadofar]

@ankitm123 @msvticket do you see this problem as well?

[msvticket]

We don't use ASM

I had other problems when trying to use it so I reverted to vault

[babadofar]

Got this fixed now. First I saw that the AWS assumed role did not have permissions to update secrets. Fixed by adding the needed permissions to the role. Then by running "jx secret populate", the secrets were generated again, and now it works

[msvticket]

/area secrets