-
Notifications
You must be signed in to change notification settings - Fork 4.3k
chore(release): 2.192.0 #34246
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
Merged
Merged
chore(release): 2.192.0 #34246
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Issue # (if applicable) Closes #34156 ### Reason for this change Updating the message to provide better message ### Description of changes Simple change on the message to include key name ### Describe any new or updated permissions being added N/A ### Description of how you validated changes Local build has been successful ### Checklist - [ ] 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… and 16.00.4185.3.v1 (#34175) Ref: [Amazon RDS for SQL Server supports new minor versions for SQL Server 2019 and 2022](https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-rds-sql-server-2019-2022/) ```sh % aws rds describe-db-engine-versions --engine sqlserver-ee --query "DBEngineVersions[?EngineVersion=='15.00.4430.1.v1'].[DBEngineVersionDescription,EngineVersion,DBParameterGroupFamily,MajorEngineVersion,Status]" [ [ "SQL Server 2019 15.00.4430.1.v1", "15.00.4430.1.v1", "sqlserver-ee-15.0", "15.00", "available" ] ] % aws rds describe-db-engine-versions --engine sqlserver-ee --query "DBEngineVersions[?EngineVersion=='16.00.4185.3.v1'].[DBEngineVersionDescription,EngineVersion,DBParameterGroupFamily,MajorEngineVersion,Status]" [ [ "SQL Server 2022 16.00.4185.3.v1", "16.00.4185.3.v1", "sqlserver-ee-16.0", "16.00", "available" ] ] ``` ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…tructs (#32931) ### Issue # (if applicable) N/A ### Description of changes This PR adds L2 constructs to simplify the Application Signals enablement process. See aws/aws-cdk-rfcs#672 for more details. ### Describe any new or updated permissions being added ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) Closes #33602. ### Reason for this change There will be many cases where IAM roles will be created outside the CFn stack and used. Importing actual existing roles from AWS accounts is very convenience. It is also useful to be able to make an error if a role does not exist. On the other hand, a generic Context Provider for CloudControl API has been added in aws-cdk-cli. aws/aws-cdk-cli#138 This allows us to implement new context methods. ### Description of changes Add `Role.fromLookup` method using the new context provider. ### Describe any new or updated permissions being added ### Description of how you validated changes Both unit and integ tests. ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…4234) ### Issue # (if applicable) N/A ### Reason for this change In order to allow for more flexibility when configuring Identity Pool resources, one may need to override attributes in the role attachment. To make this process easier, we should be able to access this resource the same way as we would access the L2 resource. ### Description of changes ```ts // private readonly roleAttachment: IdentityPoolRoleAttachment; public readonly roleAttachment: IdentityPoolRoleAttachment; ``` ### Describe any new or updated permissions being added N/A ### Description of how you validated changes `yarn build && yarn test aws-cognito-identitypool` ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) Closes #33981 ### Reason for this change The SES module currently lacks a method to import an `EmailIdentity` by its ARN, which is inconsistent with many other CDK resource libraries. Supporting this would allow users to follow a consistent pattern when managing resources across CDK stacks. ### Description of changes - Added a new static method `EmailIdentity.fromEmailIdentityArn(scope, id, emailIdentityArn)` to enable importing an `EmailIdentity` by ARN. ### Describe any new or updated permissions being added No new IAM permissions are required, as this change does not perform any operations requiring permissions. It only allows referencing an existing SES Email Identity by ARN. ### Description of how you validated changes - Added unit tests in `email-identity.test.ts` to verify that the ARN is correctly parsed and the resulting `IEmailIdentity` behaves as expected. ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) N/A ### Reason for this change `AWS::ApiGateway::RestApi` has a `mode` property, but the L2 construct for API Gateway (SpecRestApi class) does not currently expose this property. Therefore, I added the `mode` property to the `SpecRestApiProps` interface. ### Description of changes - Introduced an optional `mode` property in `SpecRestApiProps`. - Created an enum class `RestApiMode` to define the possible values for `mode`. This enum includes two values: `merge` and `overwrite`. - Added unit and integration tests. - Updated the README.md for aws-apigateway. ### Describe any new or updated permissions being added No new IAM permissions are introduced. ### Description of how you validated changes - `packages/aws-cdk-lib/aws-apigateway/test/restapi.test.ts` - `packages/@aws-cdk-testing/framework-integ/test/aws-apigateway/test/integ.spec-restapi.ts` ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.*
### Issue # (if applicable) Closes #34217 ### Reason for this change - Current Chart version is 0.18.0 https://artifacthub.io/packages/helm/aws/aws-node-termination-handler/0.18.0 https://github.com/aws/aws-cdk/blob/58c2631de585b300cf8573ab423dcc75791cc3d2/packages/aws-cdk-lib/aws-eks/lib/cluster.ts#L1184-L1188 - Latest available version is 0.27.0 https://artifacthub.io/packages/helm/aws-node-termination-handler/aws-node-termination-handler - The outdated version of aws-node-termination-handler (0.18.0) is causing cluster creation failures for Kubernetes v1.25 and above. - Related: aws/aws-node-termination-handler#638 ### Description of changes Update aws-node-termination-handler chart version ### Describe any new or updated permissions being added None ### Description of how you validated changes Pass unit/integration tests ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) Closes #33722 ### Description of changes Event Rule support IAM Role ### Description of how you validated changes Unit + Integ ### 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) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
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). |
Comments on closed issues and PRs are hard for our team to see. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See CHANGELOG