Resolve "Test external secrets key versioning"

General MR

Summary

This MR addresses the testing of key versioning functionality for external secrets in the ESO. The focus was ensuring that the data field properly handles key mappings with specific versions and sub-properties from AWS Secrets Manager. The data field in the ESO configuration, specific keys and their respective versions can now be mapped directly to Kubernetes secrets. It improves flexibility.

Relevant logs/screenshots

Using the below user defined values

      secretConfiguration:
        enabled: true
        secretList:
          - name: storage-secret
            namespace: default
            source:
              provider: aws
              service: SecretsManager
              region: "us-gov-west-1"
              refreshInterval: "1m"
              auth:
                authType: "accesskey"
                accessKeyName: "chu-awssm-secret"
                accessKeyID: "access-key"
                secretAccessKey: "secret-access-key"
                serviceAccount: ""
              secrets:
                targetName: "storage-k8s"
                targetPolicy: ""
                secretKeyName:
                  key: target-secret
                  version: AWSCURRENT
                  property: testvalue

kubectl describe es storage-secret-externalsecrets -n default produces the below output

Key in AWS Secrets Manager

Linked Issue

issue

Upgrade Notices

N/A