-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(cognito-identitypool): allow multiple IdentityPoolRoleAttachment resources #31390
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
The pull request linter fails with the following errors:
PRs must pass status checks before we can provide a meaningful review. If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue # (if applicable)
Closes #23449
Reason for this change
Previously, you could not create multiple
IdentityPoolRoleAttachment
resources. This was due to an API bug that was setting the logical ID of the role attachment to be identical to the logical ID of the identity pool itself. On its own, this was OK since you can have different resources with the same logical ID (weird, but allowed), but you cannot have two resources of the same type with the same logical ID. This was causing an issue for the cases of either creating anIdentityPoolRoleAttachment
from scratch, or calling theaddRoleMappings()
method, which was creating an additionalIdentityPoolRoleAttachment
.Description of changes
The service team was contacted and have made updates on their end to alleviate this issue. In terms of changes in CDK, we have only validated their changes...
Description of how you validated changes
...by updating the integration test. Since these errors were failing at deploy time, the unit test does not need to be updated. The integration test, however, now makes two additional checks to verify these changes have been successful: it calls
addRoleMappings()
and it creates a newIdentityPoolRoleAttachment
resource. Both of these changes create a new role attachment, and map them to an identity pool which already has one, so if the deployment succeeds, we know the fix has been made.Note: as of (2024-09-10), the changes have not yet been made, so the integration test will fail. Once changes are made, I'll update the snapshots and undraft this PR for review
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license