chore(release): 2.63.0 #23933
Merged
chore(release): 2.63.0 #23933
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
…23755) Add support for dynamic timeouts referenced by a path in the state. Closes #15531 ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [x] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Fixes #23604 I have: - added startFleet to CfnCreationPolicy, including doc remarks for the property and the class. - added a unit test to test wether it is rendered correctly in the CloudFormation template. - added and ran an intergrity test in aws-appstream to verify that the Fleet is actually started. ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [x] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
PR #23813 made imports lazy, but in the resulting code, Nodejs no longer recognizes the exports when importing `aws-cdk-lib` from an ESM module. To solve this, vend two different index files: one for use by CJS imports, one for use by ESM imports. ESM modules will still try to load the entire library, so they don't benefit from the speed boost. This is unavoidable: we tried a more complex method that forced ESM to recognize the lazy module references anyway (by tricking the backwards compatibility lexer), but ESM did not experience a speed boost, indicating that it was crawling the entire module irrespective of the submodule accessor's laziness. So, we are opting for the simpler solution of vending two index files instead. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… OCI repository (#23392) Fixes #22341 It migrates assigning chart_dir from release name to chart name, to be consistent with helm-pull's target directory. I also added to integration test yet another chart deployment of a different chart. Why it's separate? Because of the way of how testing flow is working - if i understand it correctly it provisions previous snapshot, and finally after that provisions a new version of assets and test code **on top of existing**. Thanks to that i'm unable to cover my case in existing chart deployment, because when i change release name it conflicts with previously deployed (during old snapshot provisioning) chart (`UPDATE_FAILED (The following resource(s) failed to update: [Clustercharttestocichart9C188967]. ): Received response status [FAILED] from custom resource. Message returned: Error: b'Release "s3-chart-release" does not exist. Installing it now.\nError: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "ack-s3-controller" in namespace "ack-system" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "s3-chart-release": current value is "s3-chart"\n'`). Actually i successfully ran the modified integration test, but i didn't commit changes caused by yarn integ command, because i don't know which i have to commit. ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…cker (#23576) Fixes #8799 This implements an alternative variant on how to put get files into bundling containers. This is more flexible in its use cases for complex Docker setup scenarios but more complex and slower. Therefore it is not enabled as a default, but as an additional option. For details to the approach please refer to the linked issue. ---- ### All Submissions: * [X] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [X] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [x] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The checklist is ugly and mostly ignored. Another attempt at rewriting the pull request template. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Closes #23743 When providing a name with unsupported characters to an AppSync datasource, it is sanitized internally. #22378 introduced a bug where the sanitized name was no longer exposed on DataSource class instances. ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*   The above code generates the shown diff. This is due to #23743 where the name is sanitised, but not when setting `this.name`.
…o the canary L2 (#23820) This PR is to add the DeleteLambdaResourcesOnCanaryDeletion prop to the canary L2.
22 listed here 2023/1 [AWS Config now supports 22 new resource types](https://aws.amazon.com/about-aws/whats-new/2023/01/aws-config-22-new-resource-types/) 1. AWS::AmazonMQ::Broker 2. AWS::AppConfig::Environment 3. AWS::AppConfig::ConfigurationProfile 4. AWS::Cloud9::EnvironmentEC2 5. AWS::EventSchemas::Registry 6. AWS::EventSchemas::RegistryPolicy 7. AWS::EventSchemas::Discoverer 8. AWS::FraudDetector::Label 9. AWS::FraudDetector::EntityType 10. AWS::FraudDetector::Variable 11. AWS::FraudDetector::Outcome 12. AWS::IoT::Authorizer 13. AWS::IoT::SecurityProfile 14. AWS::IoT::RoleAlias 15. AWS::IoT::Dimension 16. AWS::IoTAnalytics::Datastore 17. AWS::Lightsail::Bucket 18. AWS::Lightsail::StaticIp 19. AWS::MediaPackage::PackagingGroup 20. AWS::Route53RecoveryReadiness::RecoveryGroup 21. AWS::ResilienceHub::ResiliencyPolicy 22. AWS::Transfer::Workflow and the three resource types I found while doing this conversion. - AWS::NetworkFirewall::Firewall - AWS::NetworkFirewall::FirewallPolicy - AWS::NetworkFirewall::RuleGroup
Bumps [aws-actions/stale-issue-cleanup](https://github.com/aws-actions/stale-issue-cleanup) from 5 to 6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-actions/stale-issue-cleanup/releases">aws-actions/stale-issue-cleanup's releases</a>.</em></p> <blockquote> <h2>v6 release</h2> <h2>What's Changed</h2> <ul> <li>build(deps-dev): bump prettier from 2.2.1 to 2.6.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/141">aws-actions/stale-issue-cleanup#141</a></li> <li>build(deps): bump minimist from 1.2.5 to 1.2.6 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/140">aws-actions/stale-issue-cleanup#140</a></li> <li>build(deps): bump node-fetch from 2.6.1 to 2.6.7 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/143">aws-actions/stale-issue-cleanup#143</a></li> <li>build(deps-dev): bump dotenv from 8.2.0 to 16.0.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/146">aws-actions/stale-issue-cleanup#146</a></li> <li>Added environment variable/argument use-created-date-for-ancient which if set to true uses issue created date instead of modified date for determining an ancient issue. by <a href="https://github.com/ashishdhingra"><code>@ashishdhingra</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/151">aws-actions/stale-issue-cleanup#151</a></li> <li>build(deps): bump minimatch from 3.0.4 to 3.1.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/157">aws-actions/stale-issue-cleanup#157</a></li> <li>build(deps): bump json5 from 1.0.1 to 1.0.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/160">aws-actions/stale-issue-cleanup#160</a></li> <li>build(deps-dev): bump eslint-plugin-import from 2.22.1 to 2.26.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/145">aws-actions/stale-issue-cleanup#145</a></li> <li>build(deps): bump loglevel from 1.7.1 to 1.8.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/162">aws-actions/stale-issue-cleanup#162</a></li> <li>build(deps): bump actions/checkout from 2 to 2.3.4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/86">aws-actions/stale-issue-cleanup#86</a></li> <li>build(deps): bump actions/checkout from 2.3.4 to 3.3.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/164">aws-actions/stale-issue-cleanup#164</a></li> <li>build(deps-dev): bump eslint-plugin-promise from 4.2.1 to 6.1.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/156">aws-actions/stale-issue-cleanup#156</a></li> <li>build(deps-dev): bump nock from 13.1.3 to 13.3.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/161">aws-actions/stale-issue-cleanup#161</a></li> <li>build(deps-dev): bump eslint-plugin-prettier from 3.4.0 to 4.2.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/163">aws-actions/stale-issue-cleanup#163</a></li> <li>build(deps-dev): bump eslint-plugin-import from 2.26.0 to 2.27.5 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/165">aws-actions/stale-issue-cleanup#165</a></li> <li>build(deps-dev): bump eslint from 7.32.0 to 8.32.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/166">aws-actions/stale-issue-cleanup#166</a></li> <li>build(deps-dev): bump eslint-config-prettier from 8.3.0 to 8.6.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/167">aws-actions/stale-issue-cleanup#167</a></li> <li>build(deps-dev): bump dotenv from 16.0.1 to 16.0.3 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/168">aws-actions/stale-issue-cleanup#168</a></li> <li>build(deps-dev): bump prettier from 2.6.2 to 2.8.3 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/170">aws-actions/stale-issue-cleanup#170</a></li> <li>build(deps-dev): bump jest from 27.3.0 to 29.4.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/169">aws-actions/stale-issue-cleanup#169</a></li> <li>Updated Dockerfile to use node:18-alpine3.16 image. by <a href="https://github.com/ashishdhingra"><code>@ashishdhingra</code></a> in <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/pull/173">aws-actions/stale-issue-cleanup#173</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6">https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/7de35968489e4142233d2a6812519a82e68b5c38"><code>7de3596</code></a> Updated Dockerfile to use node:18-alpine3.16 image. (<a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/issues/173">#173</a>)</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/f914f91e45e5ad011fade57b78eca9d929d6b930"><code>f914f91</code></a> Revert "Merge pull request <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/issues/169">#169</a> from aws-actions/dependabot/npm_and_yarn/jest...</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/d862d6ce51a6f0760f9a47783bfbc6e02000b172"><code>d862d6c</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/issues/169">#169</a> from aws-actions/dependabot/npm_and_yarn/jest-29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/b5fe9d4d1e85ad85b3c008e31d453e5695282721"><code>b5fe9d4</code></a> Merge branch 'main' into dependabot/npm_and_yarn/jest-29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/a4517fbf09ab5b2995d21135cafefe5965d2f8db"><code>a4517fb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/issues/170">#170</a> from aws-actions/dependabot/npm_and_yarn/prettier-2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/a934980b5b0c4e8e880931f51af2bacf962afc45"><code>a934980</code></a> build(deps-dev): bump jest from 27.3.0 to 29.4.0</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/ff03a0b6f15c9c4b00a4cd68ee35b39cfdac19dc"><code>ff03a0b</code></a> Merge branch 'main' into dependabot/npm_and_yarn/prettier-2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/2f0c6c4255e4a1e877391bbb3b79dea8d50aec3b"><code>2f0c6c4</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/aws-actions/stale-issue-cleanup/issues/168">#168</a> from aws-actions/dependabot/npm_and_yarn/dotenv-16.0.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/047f077be8dce43edfb933481a7333ae50b34354"><code>047f077</code></a> build(deps-dev): bump prettier from 2.6.2 to 2.8.3</li> <li><a href="https://github.com/aws-actions/stale-issue-cleanup/commit/483cae46c42862743c95419f2e7516ec007e8c6b"><code>483cae4</code></a> build(deps-dev): bump dotenv from 16.0.1 to 16.0.3</li> <li>Additional commits viewable in <a href="https://github.com/aws-actions/stale-issue-cleanup/compare/v5...v6">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 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>
…r clients (#23855) The AWS CDK uses `docker` for a feature subset related to building assets. For users, we already support the `CDK_DOCKER` env variable to change the container client at runtime. However contributing to the AWS CDK currently still requires a contributor to have `docker` installed. This PR extends the support for the `CDK_DOCKER` env variable to contributor tooling. For example one can now run: ```console CDK_DOCKER=finch ./scripts/foreach.sh "yarn build" CDK_DOCKER=finch ./scripts/foreach.sh "yarn test" ``` When using `finch`, the following packages do still fail tests, due to known feature gaps: ```csv @aws-cdk/aws-ec2 @aws-cdk/aws-lambda @aws-cdk/aws-lambda-go @aws-cdk/aws-lambda-python @aws-cdk/aws-lambda-nodejs @aws-cdk/aws-s3-deployment ``` --- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Construct Runtime Dependencies: * [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
…23908) Add a `pipeline.dot` file to the cloud assembly containing the graph structure of the pipeline. This change is a `chore`, not a `feat`, as I want this to be a debugging aid, but I don't want to service feature requests on it. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
As part of #23907 I updated the dependency on `@types/yargs` to be in the `15` major version to reflect the version we use in the rest of the repo. Version `15` did not have the `strictOptions` yargs method so I attempted to enable `strict()` and disable `strictCommands` but it looks like that doesn't work. Removing strict altogether. Our only other option is to keep `@types/yargs` pinned at `17.0.15` since `17.0.16` is no longer compatible with our version of typescript. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Some AWS services are only in us-west-2 region, while CDK uses the AWS CloudFormation resource specification from us-east-1 for generating L1. This change adds suppport for resource specifications from additional regions, with an explicit allow list for services supported for this region. Fixes #17893 Fixes #22565 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…ult-role-for-redshift-clusters feat(redshift): support default role for redshift clusters
aws-cdk-automation
added
auto-approve
pr/no-squash
|
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
PR was merged manually without squash
mrgrain
approved these changes
Jan 31, 2023
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). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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