chore(release): 1.102.0 #14521
Merged
chore(release): 1.102.0 #14521
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
Add additional minor versions for mysql engines. ``` $ aws rds describe-db-engine-versions --engine mysql | jq -r '.DBEngineVersions[] | [.EngineVersion]' | grep 5.6 "5.6.34" "5.6.35" "5.6.37" "5.6.39" "5.6.40" "5.6.41" "5.6.43" "5.6.44" "5.6.46" "5.6.48" "5.6.49" "5.6.51" $ aws rds describe-db-engine-versions --engine mysql | jq -r '.DBEngineVersions[] | [.EngineVersion]' | grep 5.7 "5.7.16" "5.7.17" "5.7.19" "5.7.21" "5.7.22" "5.7.23" "5.7.24" "5.7.25" "5.7.26" "5.7.28" "5.7.30" "5.7.31" "5.7.33" $ aws rds describe-db-engine-versions --engine mysql | jq -r '.DBEngineVersions[] | [.EngineVersion]' | grep 8.0 "8.0.11" "8.0.13" "8.0.15" "8.0.16" "8.0.17" "8.0.19" "8.0.20" "8.0.21" "8.0.23" ``` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
#13963) Issue: #13953 This change is to allow creation of composite alarms from alarms having spaces in their alarm name. Ref https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Composite_Alarm.html For more details please check above mentioned issue. ---- *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*
Insert zero-width spaces after periods to force line breaks. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This change allows users to address stacks located in nested assemblies, which is the common use case when dealing with pipelines. For example, suppose we have only two stacks, `stack1` and `stack1/foo/bar`, and the second one is in a sub-assembly. The table below shows the behavior of the CLI before and after: | **Subcommand** | **Pattern** | **Matched stacks (before)** | **Matched stacks (after)** | |------------------------------|----------------|-----------------------------|----------------------------| | deploy, destroy, diff, synth | ε | stack1 | stack1 | | list | ε | stack1 | stack1, stack1/foo/bar | | metadata | ε | ∅ | ∅ | | _any_ | *, --all | stack1 | stack1 | | _any_ | ** | stack1 | stack1, stack1/foo/bar | | _any_ | stack1/** | ∅ | stack1/foo/bar | | _any_ | stack1 | stack1 | stack1 | | _any_ | stack1/foo/bar | ∅ | stack1/foo/bar | where: ε = empty string (no parameters) ∅ = empty results/error ---- *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*
closes #14446 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This is an automatic backport of pull request #14444 done by [Mergify](https://mergify.io). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.io/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.io/ </details>
…s (backport #14400) (#14450) This is an automatic backport of pull request #14400 done by [Mergify](https://mergify.io). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.io/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.io/ </details>
`cd` only exists as a command on Mac, doesn't even exist on Windows ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Closes #13722 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…14394) Previously instanceIdentifiers and instanceEndpoints were readonly properties of DatabaseClusterNew, defaulting to empty arrays. However, they they were never set to the correct values after instances were added to the cluster. Those properties are now moved on to the DatabaseCluster and DatabaseClusterFromSnapshot classes where they can now actually be set to correct values. fixes #14377 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
* feat: cloudformation spec v35.0.0 * Patch incorrect "AWS::AppIntegrations::EventIntegration" * Suppress linter warning about new property * Fix casing in StepFunctions DataBrew snapshot test. Co-authored-by: AWS CDK Team <aws-cdk@amazon.com> Co-authored-by: Rico Huijbers <rix0rrr@gmail.com> Co-authored-by: Adam Ruka <adamruka@amazon.com>
Adds container name property to ContainerDefinitionProps which allows to explicitly set container name. If undefined, this default is still the node id. Closes #8044 Closes #13681 ---- *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*
fixes #14153 ---- *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*
This is a follow-up to #14470, where I forgot to notice that more services got added recently. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This commit updates `urlForObject()` to use the bucket's region instead of the stack's region when constructing the returned URL. Fixes #14149 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
A dependency on `make-runnable` was missing. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
We are running into conflicts where the toolkit stack canary is deleting bootstrap stacks before application stacks, which ends up with the `cfn-exec-role` being deleted before the application stack is deleted, causing errors. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
) Previously we use `addPropertyOverride()` when specifying launch template for a nodegroup: https://github.com/aws/aws-cdk/blob/e11d5378c33bea609ed09c998b305fdfd28999a9/packages/%40aws-cdk/aws-eks/lib/managed-nodegroup.ts#L359-L363 This is now available on new cfn spec that cdk uses. So we can safely migrate to cfn props instead of calling `addPropertyOverride()`. The unit test should still covered the changes: https://github.com/aws/aws-cdk/blob/e11d5378c33bea609ed09c998b305fdfd28999a9/packages/%40aws-cdk/aws-eks/test/test.nodegroup.ts#L565-L643 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Resolves #14502 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When using the same secret as token with different json keys only add the resource once to the policy ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This is a follow-up to #14505 which in retrospect wasn't complete. The list of stacks was ordered properly, but since all stacks were being deleted in parallel this didn't actually solve the race condition. Delete stacks in series instead. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The environment variable `STACKS_TO_VALIDATE` contains the stack hierarchical ids that should be validated after synthesis. By default (when the variable is undefined), it validates only the printed stacks, keeping backward compatibility. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
* feat: cloudformation spec v35.1.0 * chore: attribute exception Co-authored-by: AWS CDK Team <aws-cdk@amazon.com> Co-authored-by: Nick Lynch <nlynch@amazon.com>
aws-cdk-automation
added
the
pr/no-squash
|
|
RomainMuller
approved these changes
May 4, 2021
eladb
approved these changes
May 4, 2021
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