Merged
Conversation
…ns.LambdaDestination (#16896) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Superseds #17199 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
In #17327, we stripped away the stability banner for `Cfn` resources from README's of alpha modules, since these modules don't actually contain L1 resources. Problem is that this stripping causes a bunch of `pkglint` violations on the `v2-main` branch, for example: ```console @aws-cdk/aws-iot-alpha: In package package.json -- 972 | @aws-cdk/aws-iot-alpha: - [package-info/maturity] Missing stability banner for experimental in README.md file (fixable) 973 | @aws-cdk/aws-iot-alpha: Error: Some package.json files had errors 974 | @aws-cdk/aws-iot-alpha: at main (/codebuild/output/src115445882/src/github.com/aws/aws-cdk/tools/@aws-cdk/pkglint/bin/pkglint.js:30:15) 975 | @aws-cdk/aws-iot-alpha: at Object.<anonym ``` This PR fixes the transform and makes the necessary changes so that `pkglint` will be happy. Note that this was not detected during merge of #17327 into master since on master, these packages are transformed into private packages, and hence are not validated. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
By default the asset hash for a `NodejsFunction` is based on the bundling output, the result of the `esbuild` bundling. Add a `assetHash` prop to customize the asset hash and allow users to implement their own logic. This can be useful if users want to invalidate the asset based on specific (input) file contents or logic. Closes #16157 ---- *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>
…ustom resources (#17302) For PRs that contain changes to custom resources, we want to draw the author's attention to the part of the documentation that explains the important cases to handle. This workflow will create a checklist with a single item, pointing to that section of the README, in case the PR contains keywords such as `CustomResource` or `CustomResourceProvider`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add the `--verbose` switch to rosetta so that it prints statistics on time and cache effectiveness. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
As part of this PR: - chore(apigatewayv2): make examples compile - chore(apigatewayv2-integrations): make examples compile - chore(apigatewayv2-authroziers): make examples compile ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
In addition, fix up CDKv2 init templates to not refer to the alpha version of this module. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Apparently, in order to add labels to a PR, the token must have write permissions to issues as well, otherwise it will silently fail. See cli/cli#4631 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…on (#17131) At the moment, tokens in OpenSearch capacity configuration lead to errors because they are not handled correctly for instance types. This fix provides the possibility to use tokens in instance types. The changes are implemented in modules opensearch and elasticsearch. Fixes #15014. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…luster` (#16976) Auto-termination is supported with Amazon EMR versions 5.30.0 and 6.1.0 and later. This change enables CDK users to specify an auto-termination policy on EMR clusters created through the aws-stepfunctions task EmrCreateCluster. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…ame (#17348) The current method `notifiyOnPullRequestMerged` has a typo in the name. This PR is to create a method called `notifyOnPullRequestMerged` with the same functionality, minus the spelling mistake. Marks `notifiyOnPullRequestMerged` as deprecated so as not to break existing code. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Resolves #12559 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Collaborator
Author
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
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). |
This file contains hidden or 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
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