chore(release): 2.150.0 #30922
Merged
chore(release): 2.150.0 #30922
Conversation
This file contains 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
Minor typo fix in bucket error message ### 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*
They have now been standardized for a few years. We did not initially remove the old mappings out of caution and because we were unsure that the changes has made it to all regions yet. It is long past that happening at this point. Because we never removed this or marked it as deprecated, we still have a not insignificant amount of customers who believe the individual mapping is necessary and cut tickets because it is not up-to-date. ### Issue # (if applicable) Closes #<issue number here>. ### Reason for this change ### Description of changes ### Description of how you validated changes ### 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*
### Reason for this change As documented, the Node.js v16 runtime was deprecated on June 12, 2024. https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html ### Description of changes ### Description of how you validated changes ### 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*
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-bedrock │ └ resources │ ├[~] resource AWS::Bedrock::Agent │ │ └ types │ │ ├[~] type GuardrailConfiguration │ │ │ └ - documentation: Configuration information for a guardrail that you use with the `Converse` action. │ │ │ + documentation: Configuration information for a guardrail that you use with the [Converse](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_runtime_Converse.html) operation. │ │ └[~] type S3Identifier │ │ ├ - documentation: Contains information about the S3 object containing the resource. │ │ │ + documentation: The identifier information for an Amazon S3 bucket. │ │ └ properties │ │ └ S3ObjectKey: (documentation changed) │ ├[~] resource AWS::Bedrock::DataSource │ │ ├ properties │ │ │ ├ DataDeletionPolicy: (documentation changed) │ │ │ └ DataSourceConfiguration: (documentation changed) │ │ └ types │ │ ├[~] type ChunkingConfiguration │ │ │ └ properties │ │ │ └ ChunkingStrategy: (documentation changed) │ │ ├[~] type DataSourceConfiguration │ │ │ ├ - documentation: Contains details about how a data source is stored. │ │ │ │ + documentation: The connection configuration for the data source. │ │ │ └ properties │ │ │ ├ S3Configuration: (documentation changed) │ │ │ └ Type: (documentation changed) │ │ └[~] type S3DataSourceConfiguration │ │ ├ - documentation: Contains information about the S3 configuration of the data source. │ │ │ + documentation: The configuration information to connect to Amazon S3 as your data source. │ │ └ properties │ │ ├ BucketArn: (documentation changed) │ │ ├ BucketOwnerAccountId: (documentation changed) │ │ └ InclusionPrefixes: (documentation changed) │ └[~] resource AWS::Bedrock::KnowledgeBase │ └ types │ └[~] type KnowledgeBaseConfiguration │ └ - documentation: Contains details about the embeddings configuration of the knowledge base. │ + documentation: Configurations to apply to a knowledge base attached to the agent during query. For more information, see [Knowledge base retrieval configurations](https://docs.aws.amazon.com/bedrock/latest/userguide/agents-session-state.html#session-state-kb) . ├[~] service aws-cloudtrail │ └ resources │ ├[~] resource AWS::CloudTrail::EventDataStore │ │ └ types │ │ └[~] type AdvancedFieldSelector │ │ └ properties │ │ └ Field: (documentation changed) │ └[~] resource AWS::CloudTrail::Trail │ └ types │ ├[~] type AdvancedFieldSelector │ │ └ properties │ │ └ Field: (documentation changed) │ ├[~] type DataResource │ │ └ - documentation: Data events provide information about the resource operations performed on or within a resource itself. These are also known as data plane operations. You can specify up to 250 data resources for a trail. │ │ Configure the `DataResource` to specify the resource type and resource ARNs for which you want to log data events. │ │ You can specify the following resource types in your event selectors for your trail: │ │ - `AWS::DynamoDB::Table` │ │ - `AWS::Lambda::Function` │ │ - `AWS::S3::Object` │ │ > The total number of allowed data resources is 250. This number can be distributed between 1 and 5 event selectors, but the total cannot exceed 250 across all selectors for the trail. │ │ > │ │ > If you are using advanced event selectors, the maximum total number of values for all conditions, across all advanced event selectors for the trail, is 500. │ │ The following example demonstrates how logging works when you configure logging of all data events for an S3 bucket named `DOC-EXAMPLE-BUCKET1` . In this example, the CloudTrail user specified an empty prefix, and the option to log both `Read` and `Write` data events. │ │ - A user uploads an image file to `DOC-EXAMPLE-BUCKET1` . │ │ - The `PutObject` API operation is an Amazon S3 object-level API. It is recorded as a data event in CloudTrail. Because the CloudTrail user specified an S3 bucket with an empty prefix, events that occur on any object in that bucket are logged. The trail processes and logs the event. │ │ - A user uploads an object to an Amazon S3 bucket named `arn:aws:s3:::DOC-EXAMPLE-BUCKET1` . │ │ - The `PutObject` API operation occurred for an object in an S3 bucket that the CloudTrail user didn't specify for the trail. The trail doesn’t log the event. │ │ The following example demonstrates how logging works when you configure logging of AWS Lambda data events for a Lambda function named *MyLambdaFunction* , but not for all Lambda functions. │ │ - A user runs a script that includes a call to the *MyLambdaFunction* function and the *MyOtherLambdaFunction* function. │ │ - The `Invoke` API operation on *MyLambdaFunction* is an Lambda API. It is recorded as a data event in CloudTrail. Because the CloudTrail user specified logging data events for *MyLambdaFunction* , any invocations of that function are logged. The trail processes and logs the event. │ │ - The `Invoke` API operation on *MyOtherLambdaFunction* is an Lambda API. Because the CloudTrail user did not specify logging data events for all Lambda functions, the `Invoke` operation for *MyOtherLambdaFunction* does not match the function specified for the trail. The trail doesn’t log the event. │ │ + documentation: You can configure the `DataResource` in an `EventSelector` to log data events for the following three resource types: │ │ - `AWS::DynamoDB::Table` │ │ - `AWS::Lambda::Function` │ │ - `AWS::S3::Object` │ │ To log data events for all other resource types including objects stored in [directory buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html) , you must use [AdvancedEventSelectors](https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_AdvancedEventSelector.html) . You must also use `AdvancedEventSelectors` if you want to filter on the `eventName` field. │ │ Configure the `DataResource` to specify the resource type and resource ARNs for which you want to log data events. │ │ > The total number of allowed data resources is 250. This number can be distributed between 1 and 5 event selectors, but the total cannot exceed 250 across all selectors for the trail. │ │ The following example demonstrates how logging works when you configure logging of all data events for a general purpose bucket named `DOC-EXAMPLE-BUCKET1` . In this example, the CloudTrail user specified an empty prefix, and the option to log both `Read` and `Write` data events. │ │ - A user uploads an image file to `DOC-EXAMPLE-BUCKET1` . │ │ - The `PutObject` API operation is an Amazon S3 object-level API. It is recorded as a data event in CloudTrail. Because the CloudTrail user specified an S3 bucket with an empty prefix, events that occur on any object in that bucket are logged. The trail processes and logs the event. │ │ - A user uploads an object to an Amazon S3 bucket named `arn:aws:s3:::DOC-EXAMPLE-BUCKET1` . │ │ - The `PutObject` API operation occurred for an object in an S3 bucket that the CloudTrail user didn't specify for the trail. The trail doesn’t log the event. │ │ The following example demonstrates how logging works when you configure logging of AWS Lambda data events for a Lambda function named *MyLambdaFunction* , but not for all Lambda functions. │ │ - A user runs a script that includes a call to the *MyLambdaFunction* function and the *MyOtherLambdaFunction* function. │ │ - The `Invoke` API operation on *MyLambdaFunction* is an Lambda API. It is recorded as a data event in CloudTrail. Because the CloudTrail user specified logging data events for *MyLambdaFunction* , any invocations of that function are logged. The trail processes and logs the event. │ │ - The `Invoke` API operation on *MyOtherLambdaFunction* is an Lambda API. Because the CloudTrail user did not specify logging data events for all Lambda functions, the `Invoke` operation for *MyOtherLambdaFunction* does not match the function specified for the trail. The trail doesn’t log the event. │ └[~] type EventSelector │ └ properties │ └ DataResources: (documentation changed) ├[~] service aws-cognito │ └ resources │ └[~] resource AWS::Cognito::UserPoolUICustomizationAttachment │ └ attributes │ └ Id: (documentation changed) ├[~] service aws-ecs │ └ resources │ ├[~] resource AWS::ECS::Service │ │ └ types │ │ └[~] type LogConfiguration │ │ └ properties │ │ └ LogDriver: (documentation changed) │ └[~] resource AWS::ECS::TaskDefinition │ ├ properties │ │ └ Cpu: (documentation changed) │ └ types │ ├[~] type ContainerDefinition │ │ └ properties │ │ └ StartTimeout: (documentation changed) │ └[~] type LogConfiguration │ └ properties │ └ LogDriver: (documentation changed) ├[~] service aws-fsx │ └ resources │ ├[~] resource AWS::FSx::FileSystem │ │ └ types │ │ ├[~] type OntapConfiguration │ │ │ └ properties │ │ │ ├ DeploymentType: (documentation changed) │ │ │ ├ HAPairs: (documentation changed) │ │ │ ├ PreferredSubnetId: (documentation changed) │ │ │ └ ThroughputCapacityPerHAPair: (documentation changed) │ │ └[~] type OpenZFSConfiguration │ │ └ properties │ │ └ DeploymentType: (documentation changed) │ └[~] resource AWS::FSx::Volume │ └ types │ └[~] type AggregateConfiguration │ └ properties │ └ Aggregates: (documentation changed) ├[~] service aws-qbusiness │ └ resources │ ├[~] resource AWS::QBusiness::DataSource │ │ └ properties │ │ └ Configuration: (documentation changed) │ └[~] resource AWS::QBusiness::WebExperience │ └ properties │ └ RoleArn: (documentation changed) ├[~] service aws-rds │ └ resources │ └[~] resource AWS::RDS::DBInstance │ ├ properties │ │ └ AutomaticBackupReplicationRegion: (documentation changed) │ └ types │ └[~] type ProcessorFeature │ └ - documentation: The `ProcessorFeature` property type specifies the processor features of a DB instance class status. │ + documentation: The `ProcessorFeature` property type specifies the processor features of a DB instance class. └[~] service aws-sagemaker └ resources ├[~] resource AWS::SageMaker::DataQualityJobDefinition │ └ types │ └[~] type StoppingCondition │ └ - documentation: Specifies a limit to how long a model training job or model compilation job can run. It also specifies how long a managed spot training job has to complete. When the job reaches the time limit, SageMaker ends the training or compilation job. Use this API to cap model training costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. │ + documentation: Specifies a limit to how long a job can run. When the job reaches the time limit, SageMaker ends the job. Use this API to cap costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. ├[~] resource AWS::SageMaker::ModelBiasJobDefinition │ └ types │ └[~] type StoppingCondition │ └ - documentation: Specifies a limit to how long a model training job or model compilation job can run. It also specifies how long a managed spot training job has to complete. When the job reaches the time limit, SageMaker ends the training or compilation job. Use this API to cap model training costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. │ + documentation: Specifies a limit to how long a job can run. When the job reaches the time limit, SageMaker ends the job. Use this API to cap costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. ├[~] resource AWS::SageMaker::ModelExplainabilityJobDefinition │ └ types │ └[~] type StoppingCondition │ └ - documentation: Specifies a limit to how long a model training job or model compilation job can run. It also specifies how long a managed spot training job has to complete. When the job reaches the time limit, SageMaker ends the training or compilation job. Use this API to cap model training costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. │ + documentation: Specifies a limit to how long a job can run. When the job reaches the time limit, SageMaker ends the job. Use this API to cap costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. ├[~] resource AWS::SageMaker::ModelQualityJobDefinition │ └ types │ └[~] type StoppingCondition │ └ - documentation: Specifies a limit to how long a model training job or model compilation job can run. It also specifies how long a managed spot training job has to complete. When the job reaches the time limit, SageMaker ends the training or compilation job. Use this API to cap model training costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. │ + documentation: Specifies a limit to how long a job can run. When the job reaches the time limit, SageMaker ends the job. Use this API to cap costs. │ To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. │ The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . │ > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. └[~] resource AWS::SageMaker::MonitoringSchedule └ types └[~] type StoppingCondition └ - documentation: Specifies a limit to how long a model training job or model compilation job can run. It also specifies how long a managed spot training job has to complete. When the job reaches the time limit, SageMaker ends the training or compilation job. Use this API to cap model training costs. To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. + documentation: Specifies a limit to how long a job can run. When the job reaches the time limit, SageMaker ends the job. Use this API to cap costs. To stop a training job, SageMaker sends the algorithm the `SIGTERM` signal, which delays job termination for 120 seconds. Algorithms can use this 120-second window to save the model artifacts, so the results of training are not lost. The training algorithms provided by SageMaker automatically save the intermediate results of a model training job when possible. This attempt to save artifacts is only a best effort case as model might not be in a state from which it can be saved. For example, if training has just started, the model might not be ready to save. When saved, this intermediate data is a valid model artifact. You can use it to create a model with `CreateModel` . > The Neural Topic Model (NTM) currently does not support saving intermediate model artifacts. When training NTMs, make sure that the maximum runtime is sufficient for the training job to complete. ```
### Issue # (if applicable) - N/A Closes #<issue number here>- N/A ### Reason for this change Update issue-label-assign.yml to add cli-lib-alpha. ### Description of changes Update issue-label-assign.yml to add cli-lib-alpha. ### Description of how you validated changes ### 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*
…rviceCrossRegion (#30795) ### Issue # (if applicable) closes #30799 ### Reason for this change I found some AWS services uses camelCase for API parameters, such as [api-gateway](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/api-gateway/command/GetRestApiCommand/) or [bedrock-runtime](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/bedrock-runtime/command/InvokeModelCommand/). However, currently `CallAwsServiceCrossRegion` allows only PascalCase for parameters, and it throws an error if parameters are not in PascalCase. ### Description of changes Because we do not precisely know which service uses camelCase, this PR just removes the validation logic to allow both camelCase and PascalCase for parameters. This will also reduce maintanance cost in the future. ### Description of how you validated changes Added a unit test. ### 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*
…0864) ### Reason for this change I spoke with @adamjkeller the other day about a more appropriate PR link regarding the community contribution call-outs. I submit this PR on his behalf. ### Description of changes ### Description of how you validated changes ### 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*
…cluding confidential data (#30689) ### Issue # (if applicable) Closes #30275. ### Reason for this change When using a Provider to create a custom resource, the request and response objects are logged by the provider function. There is no apparent way to prevent or redact this logging, resulting in secrets being logged if returned in the custom resource's Data object. By extension, if secret values are passed in the resource's ResourceProperties they will be logged as well. ### Description of changes Allow `NoEcho` fields to mask the data response to `*****`. ### Description of how you validated changes Integ test covering this and verifeid in the log stream that `redacted` is included in the message. ### 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*
Fix wrong link in syn-nodejs-puppeteer 6.2. I discovered this while working on #30851. I was [advised](#30851 (comment)) to separate the PRs, so I'm creating this as a new PR. ### 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*
Fixed a broken link. ### 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*
…mAction (#30867) ### Issue # (if applicable) N/A ### Reason for this change Fixing a typo ### Description of changes Fixing a typo in the docs under aws-cdk-lib aws_cloudwatch Alarm addAlarmAction ### Description of how you validated changes Spell checker ### 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) None ### Reason for this change Addon L2 construct is added by #30576 but there is no documentation about it in the README.md. ### Description of changes Add Add-ons documentation to README.md ### Description of how you validated changes None ### 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*
PRs with the exemption requested label should not be marked as stale since the onus is on the maintainers to address the exemption before the contributor can satisfy our linter. Unlikely to be abused, but we can reconsider this approach if it is.
### Issue # (if applicable) Closes #30683 ### Reason for this change G6 instances are not yet supported by CDK L2 ### Description of changes Added G6 instance class ### Description of how you validated changes Added `g6` to existing unit test ### 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 #30850. ### Reason for this change Add new runtime https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Library_nodejs_puppeteer.html#CloudWatch_Synthetics_runtimeversion-nodejs-puppeteer-8.0 ### Description of changes Add new runtime ### Description of how you validated changes No test added because just add runtime enum. ### 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*
This PR cleans up the files created in a temp folder when the custom resource handlers are generated. While using a temp folder removes these files on restart, most people aren't typically in the habit of regular restarts. We are now in a position where running our integ tests and/or unit tests will cause my machine to run out of space. This is one of several PRs to fix this. This may seem like a tiny change to PR on it's own when I've just said that there will be several, but I'm intentionally keeping them small and separate. There is some behavior in our tests that I don't quite understand so small incremental change will help isolate this better. There are no tests to add here but I have run the entire test suite locally from a clean workspace after making this change. ### 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*
…102.1 (#30812) Update ADOT Lambda Layer ARNs for recent release aws-observability/aws-otel-lambda#957 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
add required permissions ### Issue # (if applicable) Closes #<issue number here>. ### Reason for this change ### Description of changes ### Description of how you validated changes ### 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*
…nt handler (#30746) ### Issue # (if applicable) Closes #30211. ### Reason for this change Original PR #30225 Currently the `s3_dest` and `old_s3_dest` are logged as received. AWS inspector has identified as HIGH findings(CWE-[117](https://cwe.mitre.org/data/definitions/117.html),[93](https://cwe.mitre.org/data/definitions/93.html) - Log injection) in the lambda code. ### Description of changes We are sanitizing the message before logging to mitigate the CWE-[117](https://cwe.mitre.org/data/definitions/117.html),[93](https://cwe.mitre.org/data/definitions/93.html) - Log injection vulnerabilites. ### Description of how you validated changes Run all the existing integ test for s3-deployment custom resource and checked the AWS inspector if the finding still exists.  ### 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*
…#30904) ### Reason for this change CloudwatchLogs recently launched support for Infrequent Access Log Group Class in china and gov cloud regions. We are adding support in CDK to use this feature. ### Description of changes Added LogGroup Class attribute support in CDK for China and GovCloud regions. This feature is already launched by CWL in china and gov-cloud regions. This PR would add CDK support for the same. ### Description of how you validated changes This feature is already has integ test coverage in commercial region. We have validated the feature on service side already. ### 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*
### Issue # (if applicable) Closes #30899. ### Reason for this change Lambda released SnapStart support for arm64 functions: https://aws.amazon.com/about-aws/whats-new/2024/07/aws-lambda-snapstart-java-functions-arm64-architecture/ ### Description of changes Allow configuring SnapStart on arm64 functions. ### Description of how you validated changes ```yarn test``` ### 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 #30863. ### Reason for this change The issue is asking to make the function `applyCloudFormationInit()` public from private. Also we have this function being public in https://github.com/aws/aws-cdk/blob/ffd9d9ce510a4c820b1437cce93c4772cd7c14c0/packages/aws-cdk-lib/aws-autoscaling/lib/auto-scaling-group.ts#L1650 ### Description of changes Make the function public ### Description of how you validated changes build passed ### 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*
) Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 44.5.5 to 44.5.6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tj-actions/changed-files/releases">tj-actions/changed-files's releases</a>.</em></p> <blockquote> <h2>v44.5.6</h2> <h2>What's Changed</h2> <ul> <li>chore(deps): update typescript-eslint monorepo to v7.14.1 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2169">tj-actions/changed-files#2169</a></li> <li>Upgraded to v44.5.5 by <a href="https://github.com/tj-actions-bot"><code>@tj-actions-bot</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2168">tj-actions/changed-files#2168</a></li> <li>chore(deps): update dependency <code>@types/node</code> to v20.14.9 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2170">tj-actions/changed-files#2170</a></li> <li>chore(deps): update dependency <code>@types/micromatch</code> to v4.0.8 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2171">tj-actions/changed-files#2171</a></li> <li>chore(deps): update dependency <code>@types/lodash</code> to v4.17.6 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2172">tj-actions/changed-files#2172</a></li> <li>chore(deps): update actions/checkout action to v3 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2173">tj-actions/changed-files#2173</a></li> <li>chore(deps): update actions/checkout action to v4 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2174">tj-actions/changed-files#2174</a></li> <li>chore(deps): update dependency <code>@types/micromatch</code> to v4.0.9 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2175">tj-actions/changed-files#2175</a></li> <li>chore(deps-dev): bump <code>@typescript-eslint/parser</code> from 7.14.1 to 7.15.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2181">tj-actions/changed-files#2181</a></li> <li>chore(deps): update dependency <code>@typescript-eslint/eslint-plugin</code> to v7.15.0 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2178">tj-actions/changed-files#2178</a></li> <li>chore(deps): update dependency <code>@types/node</code> to v20.14.10 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2182">tj-actions/changed-files#2182</a></li> <li>chore(deps): update dependency ts-jest to v29.2.0 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2184">tj-actions/changed-files#2184</a></li> <li>chore(deps): update typescript-eslint monorepo to v7.16.0 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2185">tj-actions/changed-files#2185</a></li> <li>chore(deps): update actions/setup-node action to v4.0.3 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2188">tj-actions/changed-files#2188</a></li> <li>chore(deps): update dependency ts-jest to v29.2.1 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2189">tj-actions/changed-files#2189</a></li> <li>chore(deps): update dependency ts-jest to v29.2.2 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2190">tj-actions/changed-files#2190</a></li> <li>chore(deps): update codacy/codacy-analysis-cli-action action to v4.4.2 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2191">tj-actions/changed-files#2191</a></li> <li>chore(deps): update codacy/codacy-analysis-cli-action action to v4.4.4 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2192">tj-actions/changed-files#2192</a></li> <li>chore(deps): update codacy/codacy-analysis-cli-action action to v4.4.5 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2193">tj-actions/changed-files#2193</a></li> <li>chore(deps): update dependency prettier to v3.3.3 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2194">tj-actions/changed-files#2194</a></li> <li>chore(deps): update typescript-eslint monorepo to v7.16.1 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2196">tj-actions/changed-files#2196</a></li> <li>chore(deps): update dependency <code>@types/lodash</code> to v4.17.7 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2197">tj-actions/changed-files#2197</a></li> <li>chore(deps): update dependency <code>@types/node</code> to v20.14.11 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2198">tj-actions/changed-files#2198</a></li> <li>fix(deps): update dependency <code>@octokit/rest</code> to v21.0.1 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2199">tj-actions/changed-files#2199</a></li> <li>chore(deps): update dependency eslint-plugin-prettier to v5.2.1 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2200">tj-actions/changed-files#2200</a></li> <li>chore(deps): update dependency ts-jest to v29.2.3 by <a href="https://github.com/renovate"><code>@renovate</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2203">tj-actions/changed-files#2203</a></li> <li>fix: remove unused code by <a href="https://github.com/jackton1"><code>@jackton1</code></a> in <a href="https://redirect.github.com/tj-actions/changed-files/pull/2202">tj-actions/changed-files#2202</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tj-actions/changed-files/compare/v44...v44.5.6">https://github.com/tj-actions/changed-files/compare/v44...v44.5.6</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tj-actions/changed-files/blob/main/HISTORY.md">tj-actions/changed-files's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h1><a href="https://github.com/tj-actions/changed-files/compare/v44.5.5...v44.5.6">44.5.6</a> - (2024-07-18)</h1> <h2>🐛 Bug Fixes</h2> <ul> <li>Remove unused code (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2202">#2202</a>) (<a href="https://github.com/tj-actions/changed-files/commit/6b2903bdce6310cfbddd87c418f253cf29b2dec9">6b2903b</a>) - (Tonye Jack)</li> <li><strong>deps:</strong> Update dependency <code>@octokit/rest</code> to v21.0.1 (<a href="https://github.com/tj-actions/changed-files/commit/56b5e13a32a8099659d9f0de4b06bc1fe9b60d3b">56b5e13</a>) - (renovate[bot])</li> </ul> <h2>⚙️ Miscellaneous Tasks</h2> <ul> <li><strong>deps:</strong> Update dependency ts-jest to v29.2.3 (<a href="https://github.com/tj-actions/changed-files/commit/dc82617b247f7d2e5734aa9c0a0e5b800e58c1d8">dc82617</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency eslint-plugin-prettier to v5.2.1 (<a href="https://github.com/tj-actions/changed-files/commit/1797e9a1ea6596c1ae24e354e3d27b60332efcda">1797e9a</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/node</code> to v20.14.11 (<a href="https://github.com/tj-actions/changed-files/commit/9e63ef55ed3d63a5d2a83c405c415505f18fc6ea">9e63ef5</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/lodash</code> to v4.17.7 (<a href="https://github.com/tj-actions/changed-files/commit/f1afcaced6b0126bdec60471b68db60065446b50">f1afcac</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update typescript-eslint monorepo to v7.16.1 (<a href="https://github.com/tj-actions/changed-files/commit/e42a3d1b0ac3775d2029e7f164e9969b2d0b70a3">e42a3d1</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency prettier to v3.3.3 (<a href="https://github.com/tj-actions/changed-files/commit/f0eedff3627914fdcdf6458fad3b3d27fdff3f4a">f0eedff</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update codacy/codacy-analysis-cli-action action to v4.4.5 (<a href="https://github.com/tj-actions/changed-files/commit/f6d7b721fdaf52c025f2ffecd8ed077ef7dbb8a8">f6d7b72</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update codacy/codacy-analysis-cli-action action to v4.4.4 (<a href="https://github.com/tj-actions/changed-files/commit/6f59461624f15e6b5588a64c5e2e6116135e331b">6f59461</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update codacy/codacy-analysis-cli-action action to v4.4.2 (<a href="https://github.com/tj-actions/changed-files/commit/443dcaf814b84471f1737342017b67aee4917773">443dcaf</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency ts-jest to v29.2.2 (<a href="https://github.com/tj-actions/changed-files/commit/6f8dfa84e8e84bd9098c4348fbe396887cdd0f38">6f8dfa8</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency ts-jest to v29.2.1 (<a href="https://github.com/tj-actions/changed-files/commit/df7dd40375e33c41b6fe2cd958a804c547147279">df7dd40</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update actions/setup-node action to v4.0.3 (<a href="https://github.com/tj-actions/changed-files/commit/07a5a993446b4205ab95d7f4eb2d1e435548a102">07a5a99</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update typescript-eslint monorepo to v7.16.0 (<a href="https://github.com/tj-actions/changed-files/commit/02a07463378d7af3098bbce6750f7b64e20ef461">02a0746</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency ts-jest to v29.2.0 (<a href="https://github.com/tj-actions/changed-files/commit/75ed46d2351d95449bc2a73d22be97b3e298ebd8">75ed46d</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/node</code> to v20.14.10 (<a href="https://github.com/tj-actions/changed-files/commit/c8c9e91b4862f4ad5a37964c137c76718a4cfa6f">c8c9e91</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@typescript-eslint/eslint-plugin</code> to v7.15.0 (<a href="https://github.com/tj-actions/changed-files/commit/8ead8a4214dd9c5a55cd8c8bee76d160924658d4">8ead8a4</a>) - (renovate[bot])</li> <li><strong>deps-dev:</strong> Bump <code>@typescript-eslint/parser</code> from 7.14.1 to 7.15.0 (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2181">#2181</a>) (<a href="https://github.com/tj-actions/changed-files/commit/0f83d0935656d43bd0b883e10837a93197efaaf0">0f83d09</a>) - (dependabot[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/micromatch</code> to v4.0.9 (<a href="https://github.com/tj-actions/changed-files/commit/c3dcd3e758397022af9086c80ca350d4877c8c3b">c3dcd3e</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update actions/checkout action to v4 (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2174">#2174</a>) (<a href="https://github.com/tj-actions/changed-files/commit/0e9a58eebf6df74057d390987e9c2ac0f213183f">0e9a58e</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update actions/checkout action to v3 (<a href="https://github.com/tj-actions/changed-files/commit/2295558b65fbca90682dd481b6933055f2f50dbb">2295558</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/lodash</code> to v4.17.6 (<a href="https://github.com/tj-actions/changed-files/commit/68447960fff679ad642c837ddfa08b9602eb3b1a">6844796</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/micromatch</code> to v4.0.8 (<a href="https://github.com/tj-actions/changed-files/commit/00518ab39d971ba44ba6fe89e10452323fd2674b">00518ab</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update dependency <code>@types/node</code> to v20.14.9 (<a href="https://github.com/tj-actions/changed-files/commit/2c2260e690d9c41c2c6045723778793e2552561d">2c2260e</a>) - (renovate[bot])</li> <li><strong>deps:</strong> Update typescript-eslint monorepo to v7.14.1 (<a href="https://github.com/tj-actions/changed-files/commit/d1d479f03cc2b2e212605632b30c91f85857eb16">d1d479f</a>) - (renovate[bot])</li> </ul> <h2>⬆️ Upgrades</h2> <ul> <li>Upgraded to v44.5.5 (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2168">#2168</a>)</li> </ul> <p>Co-authored-by: jackton1 <a href="mailto:17484350+jackton1@users.noreply.github.com">17484350+jackton1@users.noreply.github.com</a> (<a href="https://github.com/tj-actions/changed-files/commit/9adb9156b8a8e8484b0c33cb2fdd63f3287b0e89">9adb915</a>) - (tj-actions[bot])</p> <h1><a href="https://github.com/tj-actions/changed-files/compare/v44.5.4...v44.5.5">44.5.5</a> - (2024-06-24)</h1> <h2>⚙️ Miscellaneous Tasks</h2> <ul> <li>Remove debug lines (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2166">#2166</a>) (<a href="https://github.com/tj-actions/changed-files/commit/cc733854b1f224978ef800d29e4709d5ee2883e4">cc73385</a>) - (Tonye Jack)</li> </ul> <h2>⬆️ Upgrades</h2> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tj-actions/changed-files/commit/6b2903bdce6310cfbddd87c418f253cf29b2dec9"><code>6b2903b</code></a> fix: remove unused code (<a href="https://redirect.github.com/tj-actions/changed-files/issues/2202">#2202</a>)</li> <li><a href="https://github.com/tj-actions/changed-files/commit/dc82617b247f7d2e5734aa9c0a0e5b800e58c1d8"><code>dc82617</code></a> chore(deps): update dependency ts-jest to v29.2.3</li> <li><a href="https://github.com/tj-actions/changed-files/commit/1797e9a1ea6596c1ae24e354e3d27b60332efcda"><code>1797e9a</code></a> chore(deps): update dependency eslint-plugin-prettier to v5.2.1</li> <li><a href="https://github.com/tj-actions/changed-files/commit/56b5e13a32a8099659d9f0de4b06bc1fe9b60d3b"><code>56b5e13</code></a> fix(deps): update dependency <code>@octokit/rest</code> to v21.0.1</li> <li><a href="https://github.com/tj-actions/changed-files/commit/9e63ef55ed3d63a5d2a83c405c415505f18fc6ea"><code>9e63ef5</code></a> chore(deps): update dependency <code>@types/node</code> to v20.14.11</li> <li><a href="https://github.com/tj-actions/changed-files/commit/f1afcaced6b0126bdec60471b68db60065446b50"><code>f1afcac</code></a> chore(deps): update dependency <code>@types/lodash</code> to v4.17.7</li> <li><a href="https://github.com/tj-actions/changed-files/commit/e42a3d1b0ac3775d2029e7f164e9969b2d0b70a3"><code>e42a3d1</code></a> chore(deps): update typescript-eslint monorepo to v7.16.1</li> <li><a href="https://github.com/tj-actions/changed-files/commit/f0eedff3627914fdcdf6458fad3b3d27fdff3f4a"><code>f0eedff</code></a> chore(deps): update dependency prettier to v3.3.3</li> <li><a href="https://github.com/tj-actions/changed-files/commit/f6d7b721fdaf52c025f2ffecd8ed077ef7dbb8a8"><code>f6d7b72</code></a> chore(deps): update codacy/codacy-analysis-cli-action action to v4.4.5</li> <li><a href="https://github.com/tj-actions/changed-files/commit/6f59461624f15e6b5588a64c5e2e6116135e331b"><code>6f59461</code></a> chore(deps): update codacy/codacy-analysis-cli-action action to v4.4.4</li> <li>Additional commits viewable in <a href="https://github.com/tj-actions/changed-files/compare/cc733854b1f224978ef800d29e4709d5ee2883e4...6b2903bdce6310cfbddd87c418f253cf29b2dec9">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-cloudformation │ └ resources │ └[~] resource AWS::CloudFormation::StackSet │ └ types │ └[~] type DeploymentTargets │ └ properties │ └ AccountFilterType: (documentation changed) ├[~] service aws-codepipeline │ └ resources │ └[~] resource AWS::CodePipeline::Webhook │ ├ properties │ │ └ Authentication: (documentation changed) │ └ types │ └[~] type WebhookAuthConfiguration │ └ properties │ └ SecretToken: (documentation changed) ├[~] service aws-ec2 │ └ resources │ ├[~] resource AWS::EC2::EC2Fleet │ │ └ types │ │ └[~] type FleetLaunchTemplateOverridesRequest │ │ └ properties │ │ └ WeightedCapacity: (documentation changed) │ └[~] resource AWS::EC2::SpotFleet │ └ types │ ├[~] type LaunchTemplateOverrides │ │ └ properties │ │ └ WeightedCapacity: (documentation changed) │ └[~] type SpotFleetLaunchSpecification │ └ properties │ └ WeightedCapacity: (documentation changed) ├[~] service aws-elasticloadbalancingv2 │ └ resources │ └[~] resource AWS::ElasticLoadBalancingV2::TargetGroup │ └ types │ └[~] type TargetGroupAttribute │ └ properties │ └ Key: (documentation changed) ├[~] service aws-emr │ └ resources │ ├[~] resource AWS::EMR::Cluster │ │ └ properties │ │ └ AutoTerminationPolicy: (documentation changed) │ ├[~] resource AWS::EMR::SecurityConfiguration │ │ └ properties │ │ └ SecurityConfiguration: (documentation changed) │ └[~] resource AWS::EMR::WALWorkspace │ ├ - documentation: A WAL workspace is a logical container of write-ahead logs (WALs). All WALs in Amazon EMR WAL are encapsulated by a WAL workspace. │ │ + documentation: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-emr-walworkspace.html │ └ properties │ ├ Tags: (documentation changed) │ └ WALWorkspaceName: (documentation changed) ├[~] service aws-glue │ └ resources │ └[~] resource AWS::Glue::Job │ └ properties │ └ GlueVersion: (documentation changed) ├[~] service aws-guardduty │ └ resources │ └[~] resource AWS::GuardDuty::MalwareProtectionPlan │ └ properties │ └ Role: (documentation changed) └[~] service aws-rds └ resources ├[~] resource AWS::RDS::DBCluster │ ├ properties │ │ └ PubliclyAccessible: (documentation changed) │ └ types │ └[~] type MasterUserSecret │ └ properties │ └ SecretArn: (documentation changed) └[~] resource AWS::RDS::DBInstance ├ attributes │ └ MasterUserSecret.SecretArn: (documentation changed) └ types └[~] type MasterUserSecret └ properties └ SecretArn: (documentation changed) ```
aws-cdk-automation
added
auto-approve
pr/no-squash
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Leo10Gama
added
pr/do-not-merge
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. |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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