Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge #31

Merged
merged 16 commits into from
Oct 29, 2020
Merged

Merge #31

merged 16 commits into from
Oct 29, 2020

Conversation

flemjame-at-amazon
Copy link
Owner


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

dependabot-preview bot and others added 16 commits October 27, 2020 16:52
https://aws.amazon.com/about-aws/whats-new/2020/10/aws-cloudformation-now-supports-increased-limits-on-five-service-quotas/

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
enironment ->
environment

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…1101)

closes #10694

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Some users want to use `CfnInit` more flexibly, not with one of
our supported avenues of `Instance` or `AutoScalingGroup` (a prime
use case is AutoScalingGroups with LaunchTemplates, which we have no
L2 for yet).

To do that, they need to be able to call `CfnInit.attach()`.

This change makes that method public so users are able to call it.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…cy ARNs (#9867)

The current bootstrapping experience has sharp edges. It requires you
to pass `--cloudformation-execution-policies` in all cases, even if
you just want a "simple", same-account bootstrap stack. If you bootstrap
your own accounts, you probably don't have a centralized SecOps
team that is limiting you, and you're probably intending to deploy
everything using the CDK, which means you're looking for AdministratorAccess.

In effect, you are forced to constantly Google and copy/paste the ARN
for `AdministratorAccess` (because who can remember that)
and it's a bad experience.

In the case of bootstrapping an account just for use "by itself",
however (which is the 90% use case for bootstrapping),
the trust boundary is very clear and there's no risk of privilege
escalation between accounts.

Add an optimization where in the case of a "simple", non-cross account
bootstrap, we'll default to the AdministratorAccess ARN for you.

Once you establish `--trust` with another account, we'll still
force you to spell out the execution policy you'll want to use though.

Fixes #8571.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The collection of creation stack traces for each instanciation of a
`Lazy` object is fairly slow, and retention of the stack traces incurs a
significant toll on heap memory usage; especially in contexts where many
such instances are created.

In order to remove the performance toll of those and remove the impact
on heap allocation, while retaining the ability to get access to the
stack traces when they are useful (i.e: for debugging a resolution time
issue), the stack trace capture is now conditioned to the `CDK_DEBUG`
environment variable being set to `'true'`, which can also be set via
the new `--debug` argument of the `cdk` command line tool.

BREAKING CHANGE: Creation stack traces for `Lazy` values are no longer
captured by default. The `CDK_DEBUG=true` environment variable must be
set in order to capture stack traces (this is also achieved by using the
`--debug` option of the `cdk` CLI). Users should not need those stack
traces most of the time, and should only enable creation stack trace
captures when tyring to troubleshoot a resolution error that they are
otherwise unable to trace back.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Introduces CloudFormation init (cfn-init) support for autoscaling groups.
This builds on the previous work (#9065) and (#9664) that introduced init
support for instances.

This change also reworks the existing signaling functionality, as this becomes
even more important with cfn-init.

A final change is to export the `CloudFormationInit._attach` method and related
options.

Credit for 90% of this goes to @rix0rrr; all cfn-init support was pair-
programmed, but the ASG stuff was mostly him.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The canary runtime property determines which [synthetics runtime version](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Library.html) will be included in the lambda function created by the Synthetics service. The difference between runtime versions could be as dramatic as a change to the supported nodejs version.  Given that the "sane default" value changes as new runtime versions are released, it is better to leave it to the user to make an informed decision which version to use.

Merged the previous two integration tests so it will be easier to test. 

BREAKING CHANGE: `runtime` is now a required property.  
 


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…in Developer Preview (#11180)




----

*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.778.0 to 2.781.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.778.0...v2.781.0)

Signed-off-by: dependabot-preview[bot] <[email protected]>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Bumps [ts-jest](https://github.com/kulshekhar/ts-jest) from 26.4.2 to 26.4.3.
- [Release notes](https://github.com/kulshekhar/ts-jest/releases)
- [Changelog](https://github.com/kulshekhar/ts-jest/blob/master/CHANGELOG.md)
- [Commits](kulshekhar/ts-jest@v26.4.2...v26.4.3)

Signed-off-by: dependabot-preview[bot] <[email protected]>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
This new version includes the `node.addr` property which deprecates `uniqueId`.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
fixes #11161


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This library is being checked by pkglint to ensure a minimum compatible version is honored.
As long as this requirement exists, the workflow cannot automatically upgrade constructs
without causing a build break, which is undesirable in this context.
@flemjame-at-amazon flemjame-at-amazon merged commit 9a9d863 into flemjame-at-amazon:master Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants