Failure when injecting a dynamic key pair into a k8s secret

[awilliams-bb]

Issue:
When using a dynamic service like AWS Engine in Vault, the key pairs do not match, leading to a bad set of credentials. The issue is caused due to the webhook making separate calls to the AWS Engine (and generating two separate key pairs) for the access key and secret key, resulting in a set of non-matching keys.

Values Example:
vault:aws/creds/my-role#access_key
vault:aws/creds/my-role#secret_key

Using AWS Engine: https://banzaicloud.com/docs/bank-vaults/external-configuration/secrets-engines/#aws

Expected result:
When the webhook reaches out to inject values into a k8s secret, the values are added from a single request to the AWS Engine.

/kind bug

[github-actions]

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

[github-actions]

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.