chore(release): 1.140.0 #18568
Merged
chore(release): 1.140.0 #18568
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
---- This PR adds support for requiring an API Key on Websocket API routes. Specifically, it does the following: * Exposes `apiKeyRequired` on route object (defaults to false) * Exposes `apiKeySelectionExpression` on api object In addition, the following has been added: * Logic to ensure `apiKeySelectionExpression` falls within the two currently supported values * Created a few basic integration tests for the api and route objects for websockets *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The stability and long-term prospects of colors is unclear; remove our dependency and start using chalk instead. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
According to the docs on CodeBuild [build transitions], the `POST_BUILD` step is always run after `BUILD`, even if `BUILD` fails. This can mean in our pipeline we can fail the build, and then wait for the (currently very expensive) packing step to run completely before the job fails. This change short-circuits the logic so we only run pack if the build succeeded. [build transitions]: https://docs.aws.amazon.com/codebuild/latest/userguide/view-build-details.html ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…on` (#18356) By #18321 (comment) BREAKING CHANGE: the class `FirehoseStreamAction` has been renamed to `FirehosePutRecordAction` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add a `format` option to choose the output format (CommonJS or ECMAScript module). Generate a `index.mjs` file when the ECMAScript module output format is chosen so that AWS Lambda treats it correctly. See https://aws.amazon.com/about-aws/whats-new/2022/01/aws-lambda-es-modules-top-level-await-node-js-14/ See https://aws.amazon.com/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/ Closes #13274 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Co-authored-by: AWS CDK Team <aws-cdk@amazon.com>
The buildspec was recently altered (in #18365) to skip the `POST_BUILD`/pack step if the build failed; however, the command used was bash-specific and not compliant with CodeBuild. Rewrite the check to be sh-compliant. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… policy (#18225) The AWS Management console and CloudFormation support to set a number of noncurrent versions to be retained for S3 lifecycle transitions as described in #17996. This pull request introduces the property for S3 lifecycle configurations as an optional property to CDK. The maximum supported number of noncurrent versions that could be retained is 100 which is also documented for the new property. However, no additional check is inserted if the number set by the developer is actually between 0 and 100. If this check is desired, a discussion would be good on how to achieve throwing an error as I don't see a smooth solution. Resolves #17996. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Previously, bootstrap downgrading is an error. That is, when the bootstrap stack is currently version '9', and you're trying to run `cdk bootstrap` with version '8', the command will currently fail. This makes it hard to script around, and in fact this is causing us problems in the pipeline where we unconditionally run `cdk bootstrap` and an accidentally upgraded bootstrap stack fails all tests. This is happening for no good reason, since the bootstrap stacks are backwards compatible. Turn this case from an error into a successful no-op. ---- *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.
…ations (#18154) Add support for integration subtype and credentials allowing to extend `HttpRouteIntegration` to create integrations for AWS services. See https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-aws-services.html Extracted part of #16287 to make it more reviewer friendly. BREAKING CHANGE: `HttpIntegrationType.LAMBDA_PROXY` has been renamed to `HttpIntegrationType.AWS_PROXY` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
resolves #15008 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…18159) This adds a new `--logs` flag on `cdk watch` which is set to `true` by default. Watch will monitor all CloudWatch Log groups in the application and stream the log events back to the users terminal. re #18122 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…ension (#17802) ---- This PR deprecates one of the existing `scaleOnCpuUtilization` extension. We recommend users to configure task auto scaling using the [`autoScaleTaskCount`](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk-containers/ecs-service-extensions/lib/service.ts#L61) in the `Service` construct. Related PR: #17101 *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…r extensions (under feature flag) (#17817) ---- This PR adds a default `awslogs` log driver to the application container. We first check if any other observability extensions (e.g. `FirelensExtension`) have already been added to the service. It will add the log driver only if no such loggers have been enabled. *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Respect passed log group `region` when constructing an instance of `AwsLogDriver`. That change allows to implement cross region logging pattern for ECS containers. fixes #17747 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The tests were failing for me on a fresh install with:
```
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "TypeError: sm.getSecretValue is not a function".] {
code: 'ERR_UNHANDLED_REJECTION'
}
```
There were two issues:
* `expect(...).resolves` is not a fully-formed assertion. Some assertion
needs to be made on the result of the resolution, and it nees to be
awaited.
* Due to the incomplete mocking, `sm.getSecretValue` would be a
`fn.mock` constructor, instead of an object.
I'm not sure how this ever used to work, but this fixes it.
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
We are currently releasing both v1 and v2 streams of the CDK in parallel, with changes landing on v1 before they land on v2. By default, CDK Pipelines will use the "latest" CLI version. However, because "latest" always comes from the v2 version stream (since that has the highest number), there may be changes to the cx protocol in a v1 app that aren't supported by the v2 CLI yet. The "correct" solution to this would be one of (a) releasing v1 and v2 synchronously and making sure both have the same change set; or (b) not having a v2 CLI at all. Both of these would require significant engineering effort to resolve though. In the mean time, add the concept of a "preferred CLI version" to CDK Pipelines, set to `1` for most packages but to `2` for `aws-cdk-lib`, and have NPM install the "latest" CLI from the same version stream that the library is from. Fixes #18370. ---- *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*
---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Adding version 2.09.3 for Aurora MySQL ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Co-authored-by: AWS CDK Team <aws-cdk@amazon.com>
Using nullish coalescing so that it defaults to `true` only if `enabled` is `null` or `undefined`. Fixes #18402. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Adds Identity Pool L2 Construct which to date has not been implemented. Since Identity Pool's can't be used without default auth and unauth roles, also incorporated the L1 CfnIdentityPoolRoleAttachment into the Construct. Contains unit and integration tests as well as fully updated ReadMe. *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Also made an issue for this (#18431) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Removes two duplicate "the" instances in the `CONTRIBUTING.md` doc. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
) Make both sets of helper methods (`FeatureFlags.of(..).isEnabled` and `testFutureBehavior`/`testLegacyBehavior`) more prominent, and clean up the language around v2 and flipping behavior there, as that's no longer relevant. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add support for Hpc6a instances (high performance computing). [Announcement](https://aws.amazon.com/about-aws/whats-new/2022/01/amazon-ec2-hpc6a-instances/) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
I removed 3 tests that seem pointless, but I opened an issue to investigate further: #18519 It really seems like the scenario they were testing (omiting the cluster and only providing vpc) is not a working scenario anyway. ---- *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.
---- *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*
---- *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*
In order to be able to release decdk independently and iterate quickly we have migrated it to https://github.com/cdklabs/decdk (history preserved). ---- *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*
---- *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*
---- *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*
Co-authored-by: AWS CDK Team <aws-cdk@amazon.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: AWS CDK Team <aws-cdk@amazon.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
This PR is complete when these 16 modules are accounted for: - [x] route53 - [x] route53-targets - [x] route53-patterns - [x] elasticloadbalancingv2 - [x] elasticloadbalancingv2-targets - [x] elasticloadbalancingv2-actions - [x] elasticloadbalancing - [x] cloudfront - [x] cloudfront-origins - [x] secretsmanager - [x] ec2 - [x] certificates-manager - [x] sns-subscriptions - [x] sqs - [x] ssm - [x] kms ---- *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*
The logic was partly copied from the function with the same name from `assert-internal`, but the implementation was changed to use [minimatch](https://github.com/isaacs/minimatch). This way, we can have a well-known and stable contract for the matcher. Closes #18051. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…8554) The validation was too eager, causing a validation error before the actual lookup happened. Add a property to `SelectedSubnets` to make it clear in consuming code that validation shouldn't happen yet. Fixes #17600. ---- *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*
The current link to the gitpod section does nothing. This will fix the link to the correct section of CONTRIBUTING.md ---- *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
|
|
RomainMuller
approved these changes
Jan 20, 2022
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