Skip to content
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

chore(release): 2.181.1 #33612

Merged
merged 4 commits into from
Feb 27, 2025
Merged

chore(release): 2.181.1 #33612

merged 4 commits into from
Feb 27, 2025

Conversation

Leo10Gama
Copy link
Member

See CHANGELOG

Leo10Gama and others added 3 commits February 27, 2025 14:12
…rrectly (#33609)

### Issue # (if applicable)

Closes #33510 

### Reason for this change

A previous change ([PR33305](#33305)) removed the `IdentityPoolRoleAttachment` L2 construct, which also changed the creation logic of the default role attachment in the `IdentityPool` L2. This not only triggered redeployments, but did not allow for redeployment at all, as the new role attachment (with a different resource hash) was trying to be created before the old one was removed. This led to failed deployments, as only one role attachment can exist per identity pool.

### Description of changes

Brought back the `IdentityPoolRoleAttachment` L2 logic to prevent redeployment for customers using CDK `<v2.179.0`. However, the construct is now no longer being exported, which preserves the original intention of preventing confusion about using this resource.

### Describe any new or updated permissions being added

N/A

### Description of how you validated changes

`yarn test && yarn integ test/integ.identitypool.js --update-on-failed`

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

**BREAKING CHANGE**: Any `IdentityPool` resources deployed in versions `>=2.179.0` will now fail to deploy. You will need to delete the `IdentityPoolRoleAttachment` from your stack via the console before redeploying.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@Leo10Gama Leo10Gama added the pr/no-squash This PR should be merged instead of squash-merging it label Feb 27, 2025
@aws-cdk-automation aws-cdk-automation requested a review from a team February 27, 2025 22:25
@github-actions github-actions bot added the p2 label Feb 27, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Feb 27, 2025
@github-actions github-actions bot requested a review from a team as a code owner February 27, 2025 22:31
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This review is outdated)

@Leo10Gama
Copy link
Member Author

Exemption Request: I didn't make those changes, the automation pushed them

@aws-cdk-automation aws-cdk-automation added the pr-linter/exemption-requested The contributor has requested an exemption to the PR Linter feedback. label Feb 27, 2025
@Leo10Gama Leo10Gama added pr-linter/analytics-metadata-change and removed pr-linter/exemption-requested The contributor has requested an exemption to the PR Linter feedback. labels Feb 27, 2025
@aws-cdk-automation aws-cdk-automation dismissed their stale review February 27, 2025 23:00

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: d814408
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

mergify bot commented Feb 27, 2025

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 9be0d22 into v2-release Feb 27, 2025
19 checks passed
@mergify mergify bot deleted the patch/v2.181.1 branch February 27, 2025 23:01
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
contribution/core This is a PR that came from AWS. p2 pr/no-squash This PR should be merged instead of squash-merging it pr-linter/analytics-metadata-change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants