AWSCURRENT should be default version when using AWS Secrets Manager

[andrewhibbert]

Describe the bug

If you change a secret, it does not seem to go "Out of sync" and stays as AWSPREVIOUS unless you have #AWSCURRENT at the end of the secret. Ideally it should be AWSCURRENT by default

To Reproduce Steps to reproduce the behavior:

• Create a secret in secrets manager
• Refer to it in argocd (without #AWSCURRENT at the end)
• Change it
• It does not go "Out of sync"
• Add #AWSCURRENT at the end of the secret path
• It will go "Out of sync"

Expected behavior

Should default to AWSCURRENT and notice the secret change

[werne2j]

When you change the secret you have to do a hard refresh. It goes out of sync because you change the yaml triggering the out of sync.

we rely on aws secret manager to handle any defaults, we don’t set them.