Open sicoyle opened 1 week ago
/ok-to-test
The build status is currently not updated here. Please visit the action run below directly.
Commit ref: 0e4401cbc99b84a7144d9f2703933af8a8b799d3
Commit ref: 0e4401cbc99b84a7144d9f2703933af8a8b799d3
These tests failed:
Commit ref: 0e4401cbc99b84a7144d9f2703933af8a8b799d3
These tests failed:
so this PR is missing the assume role auth profile, right?
https://github.com/dapr/components-contrib/pull/3607/files yes, didn't want to bring in a bunch into this 1 PR, but after I get the kafka PR merged then this will be an easy add here.
Pls give me a sec on this PR bc I do need to make tweaks, but doing the kafka PR first.
Description
Add IAM Roles Anywhere auth profile to PostgreSQL components.
I saw where we've had fields like
awsAccessKey
andawsSecretKey
fields specific to postgres. However, in the AWS built in profiles for authentication we haveaccessKey
andsecretKey
. I've moved things to where we have some TODO comments to remove those aws prefixed fields in Dapr 1.17; however, to not break existing users, we cannot just remove these additional fields. Due to this, I had to manually manipulate the metadata bundle even further unfortunately. This is something we should never do. However, again in the case of the auth profile titled"AWS: Access Key ID and Secret Access Key"
I am forced to update the manipulations further to make the normally requiredaccessKey
andsecretKey
fields as non-required as we make a transition in the next two releases to the normalized AWS auth profile fields without theaws
prefix.AWS Auth profiles with these changes:
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: