chore(release): 1.98.0 #14112
Merged
chore(release): 1.98.0 #14112
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
) Using the same `EdgeFunction` in multiple stacks correctly created multiple stacks in `us-east-1` but with the same SSM parameter name. As a consquence, only one stack could be deployed. Fix it by including the stack unique address in the SSM parameter name. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Adds feature as requested in issue #13816 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The Java init templates were recently fixed to use `new` instead of the builder, because the builder would instantiate the wrong class (`Stack` instead of `MyStack`) (#13988). However, the structure was changed to have 3 different `new` calls in 3 different comment blocks. Change it back to the old structure: there is one instantiation, and uncommenting just passes or doesn't pass the `env` property. Except this time we use `new` instead of the builder. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The UsagePlanKey resource connects an ApiKey with a UsagePlan. The API Gateway service does not allow more than one UsagePlanKey for any given UsagePlan and ApiKey combination. For this reason, CloudFormation cannot replace this resource without either the UsagePlan or ApiKey changing. A feature was added back in Nov 2019 - 142bd0e - that allows multiple UsagePlanKey resources. The above limitation was recognized and logical id of the existing UsagePlanKey was retained. However, this unintentionally caused the logical id of the UsagePlanKey to be sensitive to order. That is, when the 'first' UsagePlanKey resource is removed, the logical id of the what was the 'second' UsagePlanKey is changed to be the logical id of what was the 'first'. This change to the logical id is, again, disallowed. To get out of this mess, we do two things - 1. introduce a feature flag that changes the default behaviour for all new CDK apps. 2. for customers with existing CDK apps who are would want to remove UsagePlanKey resource, introduce a 'overrideLogicalId' option that they can manually configure with the existing logical id. fixes #11876 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
With #13570, it is now possible to set the protocol version for ALB target groups, and thus make it working for GRPC. However, it is not yet possible to define a GrpcCode for the matcher (see [CloudFormation doc](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticloadbalancingv2-targetgroup-matcher.html)). I added a `healthyGrpcCodes` working the same way as `healthyHttpCodes`. closes #13947 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Intentionally using `chore` so it won't show up in the CHANGELOG ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Intentionally setting to `chore` so it will not show up in the CHANGELOG ---- *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*
) `@aws-cdk/assert` will be a publish-only package: we no longer use it to test our own packages. Instead, our own packages are tested using `@aws-cdk/assert-internal`. `@aws-cdk/assert` will be built by cloning the `assert-internal` package, and made to depend on either `@aws-cdk/core` on the v1 branch, and `aws-cdk-lib` on the v2 branch. ---- The `rewrite-imports` script has been moved to a top-level tools package, `aws-cdk-migration`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
`aws-cdk-lib` needs to have no dependencies (except for `constructs`), and we don't want to support this package as part of its public API. Therefore, it needs to be bundled into all packages that consume it. NPM has a bug that makes it impossible to `bundledDependencies` a package that is linked from the monorepo. We tried to work around that bug but it blocked our build because the `.tgz` is sometimes not available during the `postpack` phase (#13933). Simplest way around this now is to just copy/paste the implementation of `yaml-cfn` 3 times. Should we ever need to bundle monorepo dependencies again in the future, we can try to revive the `postpack` solution of #13933. ---- *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.
Following #11242, we also want to enable encryption at rest by default. Since switching to `true` requires a resource replacement, this PR introduces the default change behind a feature flag. New projects created with `cdk init` will have encryption enabled by default, and existing projects won't be affected. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
As part of Amazon's ongoing effort to support inclusive language, this change removes or deprecates uses of "whitelist" or "blacklist" from our public APIs (where possible), in favor of "allowlist" and "denylist". All public API elements were deprecated and new elements created. In cases where this means two possible inputs can be supplied (e.g., both whitelist and allowlist), I added checks to validate that only one was supplied. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…#14049) The 'strip deprecated' functionality has a bug when a deprecated interface is inherited by a non-deprecated interface and they both live in different files. The problem arises due to the 'import' statement being stripped ahead of the heritage clause. Temporarily turn off stripping deprecated symbols to unblock CI, until a fix is available. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…re used. (#13970) Name validation for state machines was added in #13387. The validation added was not considering that the name may contain an unresolved token. This change skips name validation if there is an unresolved token as it does not make sense to attempt to validate something that is unknown. This change also allows a few more special characters as they are allowed through the AWS Console. fixes #13946 #13912 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Move `@aws-cdk/aws-glue` dependency to `devDependencies` and introduce the necessary lint eslint exclusions since the only usage is in the integration tests, not runtime. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Fix typo ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
As it turns out, RDS stores the name of the SubnetGroup in lowercase on the server-side.
The problem is that we weren't changing the case in CloudFormation,
and thus expressions like `{ Ref: SubnetGroup }` were using the wrong casing,
resulting in the RDS service failing with a 404 error when providing a name for the SubnetGroup.
Fixes #13976
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Closes #14039 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The current heading levels for the [AppSync Docs](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-appsync-readme.html) seem not aligned. This PR tries to introduce better nesting: * group examples under example heading * move headings under Aurora Serverless one level up * group types under GraphQL Types ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Adding new version for Aurora MySQL ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
aws-cdk-automation
added
the
pr/no-squash
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
njlynch
approved these changes
Apr 12, 2021
|
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