chore(release): 1.83.0 #12374
Merged
chore(release): 1.83.0 #12374
Conversation
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
Bumps [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli) from 0.25.0 to 0.26.0. - [Release notes](https://github.com/igorshubovych/markdownlint-cli/releases) - [Commits](igorshubovych/markdownlint-cli@v0.25.0...v0.26.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
….1 (#12322) Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 4.9.0 to 4.11.1. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v4.11.1/packages/eslint-plugin) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Bumps [table](https://github.com/gajus/table) from 6.0.4 to 6.0.7. - [Release notes](https://github.com/gajus/table/releases) - [Commits](gajus/table@v6.0.4...v6.0.7) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Closes #12310. ---- *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 #12136 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
We were passing (by mistake) an unrecognized property to the `table` module. This didn't use to be a problem, but the `table` module has suddenly started throwing an "invalid config" error. The cause is a dependency update that happened today. * In #12324, the version of `table` was updated from `6.0.4` to `6.0.7`. * In [6.0.5](https://github.com/gajus/table/releases/tag/v6.0.5), `table` changes the way it does JSON validation of the input configuration ob ject. Didn't dive into all of the changes, but it stands to reason the validator has become more strict and where it *used* to allow additional properties (probably by accident) it no longer does so. Undo the passing of the unused property. This change is a **chore** instead of a **fix** because the change wasn't released yet. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
---- Recently helped someone through using this .fromString with a JsonPath. While the Overview README for the module has a good example I felt it would help by copying that example down here, so that it's immediately obvious with intellisense help. *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Closes #12301 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
#12308 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
---- Fixes #11951. Update `desiredCount` to be optional in compliance with aws/containers-roadmap#493 (comment). *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Bumps [@types/promptly](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/promptly) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/promptly) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Remove the tentative property override and use the L1 property instead. Fixes: #12154 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
`DefaultSynthesizer` parameters can contain token-like things (they can contain magic placeholder strings), but they can't be literal tokens, which is an easy mistake to make. Check for this and give a helpful error message. Fixes #12161 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Bumps [uuid](https://github.com/uuidjs/uuid) from 8.3.1 to 8.3.2. - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md) - [Commits](uuidjs/uuid@v8.3.1...v8.3.2) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Add the `repositoryCloneUrlGrc` property to expose the HTTPS GRC clone URL. HTTPS (GRC) is the protocol to use with git-remote-codecommit (GRC). It is the recommended method for supporting connections made with federated access, identity providers, and temporary credentials. See https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-git-remote-codecommit.html ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The `EdgeFunction` construct copied some patterns from CodePipelines to enable cross-environment interaction. One key difference is that for Lambda@Edge, CDK assets are created in the cross-environment support stack. This isn't supported by the BootstraplessSynthesizer, so this custom logic (copied from CodePipelines) needs to be removed. The EdgeFunction support stack will now use whatever synthesizer is default for the current stack. fixes #12172 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.804.0 to 2.822.0. - [Release notes](https://github.com/aws/aws-sdk-js/releases) - [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-js@v2.804.0...v2.822.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
chore(ecs): remove the property override for circuit breaker Fixes: #12345 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
In a recent CloudFormation specification update, the `Handler` and `Runtime` properties of the `AWS::Lambda::Function` resource were made optional. This resulted in the hash calculation of the current Version to change, as it uses the stringified output of the resource JSON, and our L1 code generation sorts properties alphabetically, but the required ones always first - the resulting order change of the keys resulted in a different hash. The quick fix for that was to amend the specification to keep those two properties required, but of course that has an adverse effect on our L1 usability. Make the hash calculation stable with regards to optional properties by sorting the historically required ones first. This is future-proof, as there will never be more required properties added to the Function resource (as that would be a backwards-incompatible change). ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
cdk_asset asset handlers use IAws to make calls to AWS APIs to discover
information about target environment: account id, region, partition.
Each asset is described by its manifest in a Cloud Assembly. This manifest
can contain placeholders to resolve by asset handlers when publishing
assets.
Previously `${Aws::Partition}` placeholder was derived from a code path used
to resolve `${Aws::AccountId}`, which was introducing a cyclic dependency for
cross account deployments:
- to replace partition placeholder it was assuming role in a target account
to discover partition
- to assume role in a target account it needs to know full role ARN to assume
- role ARN contains partition placeholder
It was working for same account deployments and for non environment aware deployments,
because SdkProvider was always using current default (ambient) credentials without making
`AssumeRole` call, thus it was able to replace placeholders in asset manifest without
introducing a cyclic dependency.
To fix cross account deployments we introduce `IAWS.discoverPartition()` method to return
partition of default (ambient) credentials `cdk deploy` is called with. This works, because
cross partition `AssumeRole` calls are not possible, therefore it's enough to know our
default credentials partition.
Fixes #12151
----
*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
force-pushed
the
bump/1.83.0
branch
from
d29cccf to
1818d2d
Compare
|
|
RomainMuller
approved these changes
Jan 6, 2021
rix0rrr
approved these changes
Jan 6, 2021
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). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
17 participants
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