Merge pull request aws#6735 from aws/bump/1.28.0

chore(release): 1.28.0

.github/ISSUE_TEMPLATE/tracking.md

@@ -21,7 +21,13 @@ service’s CDK Construct Library API reference page.
 
 
 [AWS Docs](url)  <!-- replace `url` with link to the relevant AWS Docs -->
-[CDK API Reference](url) <!-- replace `url` with link to the service's CDK API reference -->
+
+### Maturity: CloudFormation Resources Only
+<!--
+The valid maturity states are: CloudFormation Resources Only, Experimental, Developer Preview, Stable
+-->
+
+See the [AWS Construct Library Module Lifecycle doc](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) for more information about maturity levels.
 
 
 ### Implementation:
@@ -31,6 +37,7 @@ Checklist of use cases, constructs, features (such as grant methods) that will s
 - [ ] 
 - [ ]
 -->
+See the [CDK API Reference](url) for more implementation details.<!-- replace `url` with link to the service's CDK API reference -->
 
 
 

.github/workflows/pr-linter.yml

@@ -21,3 +21,4 @@ jobs:
           check: MANDATORY_CHANGES
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+

CHANGELOG.md

@@ -2,6 +2,55 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [1.28.0](https://github.com/aws/aws-cdk/compare/v1.27.0...v1.28.0) (2020-03-16)
+
+
+### ⚠ BREAKING CHANGES
+
+* **batch:** `computeEnvironments` is now required
+* **batch:** the `allocationStrategy` property was moved from `ComputeEnvironmentProps` to the `ComputeResources` interface, which is where it semantically belongs.
+* **custom-resources:** `getDataString` was renamed to `getResponseField`.
+* **custom-resources:** `getData` was renamed to `getResponseFieldReference`.
+* **custom-resources:** `catchErrorPattern` was renamed to `ignoreErrorCodesMatching`. In addition, a few synth time validations were added when using this property. See [Error Handling](https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/custom-resources#error-handling-1) for details.
+* **custom-resources:** `policyStatements` property was removed in favor of a required `policy` property. Refer to [Execution Policy](https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/custom-resources#execution-policy-1) for more details.
+
+### Features
+
+* **amplify:** App, Branch and Domain ([#5177](https://github.com/aws/aws-cdk/issues/5177)) ([e126048](https://github.com/aws/aws-cdk/commit/e126048ccae3965eb1c65ab748b1e670d75f9e44))
+* **apigateway:** authorizationScopes for a Method ([#6502](https://github.com/aws/aws-cdk/issues/6502)) ([3887cd2](https://github.com/aws/aws-cdk/commit/3887cd2d16a5bdf3cfde535e614c475aa0263c6b))
+* **apigateway:** DomainName supports SecurityPolicy ([#6374](https://github.com/aws/aws-cdk/issues/6374)) ([e8c2e0c](https://github.com/aws/aws-cdk/commit/e8c2e0c6483d5b245577af64ec535818c522e93b))
+* **apigateway:** rate limited API key ([#6509](https://github.com/aws/aws-cdk/issues/6509)) ([040906f](https://github.com/aws/aws-cdk/commit/040906f86899d8429f0429e840ed6642dc0bb527)), closes [#6405](https://github.com/aws/aws-cdk/issues/6405)
+* **batch:** ec2 launch template support ([#6602](https://github.com/aws/aws-cdk/issues/6602)) ([2b02693](https://github.com/aws/aws-cdk/commit/2b02693d1432ce7bce5bf0a78fe4a9175dd6ad91))
+* **cfnspec:** cloudformation spec v11.3.0 ([#6598](https://github.com/aws/aws-cdk/issues/6598)) ([ee3a530](https://github.com/aws/aws-cdk/commit/ee3a5300eb9ec44b12fec6c70ad018f42e182859))
+* **cli:** pass CloudFormation parameters to "cdk deploy" ([#6385](https://github.com/aws/aws-cdk/issues/6385)) ([6551124](https://github.com/aws/aws-cdk/commit/6551124794b63a6b9a1de179fdc9a27ba10e0dfb)), closes [#1237](https://github.com/aws/aws-cdk/issues/1237)
+* **core:** duration.toHumanString() ([#6691](https://github.com/aws/aws-cdk/issues/6691)) ([d833bea](https://github.com/aws/aws-cdk/commit/d833bead0fc22bf7eaeb7e369d789e4262b3ee5f))
+* **custom-resources:** enforce user opt-in when auto-generating SDK call policies ([0f5c24e](https://github.com/aws/aws-cdk/commit/0f5c24ed23cd2d394ffbab7f883c43a537747777)), closes [#5873](https://github.com/aws/aws-cdk/issues/5873)
+* **custom-resources:** log retention for AwsCustomResource ([#6698](https://github.com/aws/aws-cdk/issues/6698)) ([bf5ab69](https://github.com/aws/aws-cdk/commit/bf5ab69fd8c7b25386f7bf5d8cf607f87a22cba4))
+* **custom-resources:** module is now stable :) ([#6584](https://github.com/aws/aws-cdk/issues/6584)) ([a2a738c](https://github.com/aws/aws-cdk/commit/a2a738cf5df369b92c4039fc7442adddc2350180))
+* **custom-resources:** rename `catchErrorPattern` to `ignoreErrorCodesMatching` ([#6553](https://github.com/aws/aws-cdk/issues/6553)) ([94599f8](https://github.com/aws/aws-cdk/commit/94599f8b95d950dd7efba15c925d7c918ed111ff)), closes [#5873](https://github.com/aws/aws-cdk/issues/5873)
+* **custom-resources:** rename `getData*` to `getResponseField*` ([#6556](https://github.com/aws/aws-cdk/issues/6556)) ([d5867b4](https://github.com/aws/aws-cdk/commit/d5867b40e144464e033f24a83947cab0aee93fdb)), closes [#5873](https://github.com/aws/aws-cdk/issues/5873)
+* **dynamodb:** expose stream features on ITable ([#6635](https://github.com/aws/aws-cdk/issues/6635)) ([52e8b95](https://github.com/aws/aws-cdk/commit/52e8b957a3750431a5e68e62e860441894f9b68c)), closes [#6344](https://github.com/aws/aws-cdk/issues/6344)
+* **efs:** create EFS file systems ([#6373](https://github.com/aws/aws-cdk/issues/6373)) ([a0fb518](https://github.com/aws/aws-cdk/commit/a0fb5187a4b0c74c32333e14af1098b0c1f25705)), closes [#6286](https://github.com/aws/aws-cdk/issues/6286) [#6286](https://github.com/aws/aws-cdk/issues/6286)
+* **elbv2:** support pathpattern array ([#6558](https://github.com/aws/aws-cdk/issues/6558)) ([c3ee413](https://github.com/aws/aws-cdk/commit/c3ee41366b3f0a59864decd47d2feea9849fd095)), closes [#6497](https://github.com/aws/aws-cdk/issues/6497)
+* **iam:** policy document from json ([#6486](https://github.com/aws/aws-cdk/issues/6486)) ([bf08988](https://github.com/aws/aws-cdk/commit/bf08988f65714a07cf1783285ceb18e025802118))
+* **prlinter:** support exempting checks from pr based on a label ([#6693](https://github.com/aws/aws-cdk/issues/6693)) ([77cbe80](https://github.com/aws/aws-cdk/commit/77cbe805c9d82278592db97f08e88414a6f66175))
+* **stepfunctions-tasks:** run batch job ([#6396](https://github.com/aws/aws-cdk/issues/6396)) ([de1a36b](https://github.com/aws/aws-cdk/commit/de1a36bb5d4c78e617f3b78a06b42dfbd45475dc)), closes [#6467](https://github.com/aws/aws-cdk/issues/6467)
+* cloudformation spec v11.4.0 ([#6700](https://github.com/aws/aws-cdk/issues/6700)) ([b28b427](https://github.com/aws/aws-cdk/commit/b28b4271a1ad9832777dd3b935c918106a0a11cb))
+
+
+### Bug Fixes
+
+* **apigateway:** type mismatch in C# when setting identitySources ([#6649](https://github.com/aws/aws-cdk/issues/6649)) ([2d3e7b1](https://github.com/aws/aws-cdk/commit/2d3e7b1daeb7b7459383f687ef1b33c639cfda80)), closes [#6538](https://github.com/aws/aws-cdk/issues/6538) [40aws-cdk/aws-apigateway/test/authorizers/integ.request-authorizer.ts#L26](https://github.com/40aws-cdk/aws-apigateway/test/authorizers/integ.request-authorizer.ts/issues/L26)
+* **batch:** `computeEnvironments` is now required for JobQueue ([#6616](https://github.com/aws/aws-cdk/issues/6616)) ([0b6c865](https://github.com/aws/aws-cdk/commit/0b6c86559d641c1ef0b8c200be84356010a88b70)), closes [#6615](https://github.com/aws/aws-cdk/issues/6615)
+* **batch:** managed compute environment now properly works with compute resources and instanceRole has correct docstring and type definition ([#6549](https://github.com/aws/aws-cdk/issues/6549)) ([4e81334](https://github.com/aws/aws-cdk/commit/4e813345b62c0db73b0c2116d5592ebcb9def3d2))
+* **certificatemanager:** Route53 endpoint cannot be set and does not work for aws-cn ([#6480](https://github.com/aws/aws-cdk/issues/6480)) ([9858cdb](https://github.com/aws/aws-cdk/commit/9858cdb1b11e9713ab83d57256ded9b9a9df7c53))
+* **cli:** codepipeline cloudformation action in cross account fail writing outputArtifacts ([#6594](https://github.com/aws/aws-cdk/issues/6594)) ([05cf78b](https://github.com/aws/aws-cdk/commit/05cf78bc9395bb3b46565bb89a264f4ede76a827))
+* **cloudwatch:** missing LessThanLowerOrGreaterThanUpperThreshold ([#6597](https://github.com/aws/aws-cdk/issues/6597)) ([9731555](https://github.com/aws/aws-cdk/commit/973155543c28af661095f3ed8edba4cf8934f70d))
+* **codepipeline-actions:** use IBaseService instead of BaseService in EcsDeployActionProps ([#6412](https://github.com/aws/aws-cdk/issues/6412)) ([bed5357](https://github.com/aws/aws-cdk/commit/bed53578df64b6a77c6a6e434c235ef4aefde300))
+* **eks:** cannot upgrade version of clusters with an explicit name ([#6064](https://github.com/aws/aws-cdk/issues/6064)) ([1dd7104](https://github.com/aws/aws-cdk/commit/1dd7104ff4510005a0b6ff14372846747c572ed1))
+* **eks:** sporadic broken pipe when deploying helm charts ([#6522](https://github.com/aws/aws-cdk/issues/6522)) ([03df1f1](https://github.com/aws/aws-cdk/commit/03df1f1c5f152ff0a14e872095df3b97b0d25fa0)), closes [#6381](https://github.com/aws/aws-cdk/issues/6381)
+* **iam:** cannot add multiple conditions using same operator ([348a952](https://github.com/aws/aws-cdk/commit/348a952db68c838d73258cd8355322e151ae1080))
+
 ## [1.27.0](https://github.com/aws/aws-cdk/compare/v1.26.0...v1.27.0) (2020-03-03)
 
 

README.md

@@ -30,7 +30,8 @@ The CDK is available in the following languages:
 [API Reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-construct-library.html) |
 [Examples](https://github.com/aws-samples/aws-cdk-examples) |
 [Getting Help](#getting-help) |
-[RFCs](https://github.com/aws/aws-cdk-rfcs)
+[RFCs](https://github.com/aws/aws-cdk-rfcs) |
+[Roadmap](https://github.com/aws/aws-cdk/blob/master/ROADMAP.md)
 
 Developers use the [CDK framework] in one of the
 supported programming languages to define reusable cloud components called [constructs], which
@@ -122,6 +123,13 @@ We welcome community contributions and pull requests. See
 [CONTRIBUTING](./CONTRIBUTING.md) for information on how to set up a development
 environment and submit code.
 
+## Roadmap
+
+The [AWS CDK Roadmap project board] lets developers know about our upcoming features and priorities to help them plan how to best leverage the CDK and identify opportunities to contribute to the project. See [ROADMAP] for more information and FAQs.
+
+[AWS CDK Roadmap project board]: https://github.com/orgs/aws/projects/7
+[Roadmap]: (https://github.com/aws/aws-cdk/ROADMAP.md)
+
 ## License
 
 The AWS CDK is distributed under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0).

ROADMAP.md

@@ -0,0 +1,86 @@
+# AWS CDK Roadmap
+
+The [AWS CDK Roadmap] lets developers know about our upcoming features and priorities to help them plan how to best leverage the CDK and identify opportunities to contribute to the project. The roadmap provides a high-level view of our work in progress across the [aws-cdk], [aws-cdk-rfcs], and [jsii] repositories, and creates an opportunity for customers to engage in a conversation with AWS CDK engineers to give us direct feedback.
+
+[AWS CDK Roadmap]: https://github.com/orgs/aws/projects/7
+[aws-cdk]: https://github.com/aws/aws-cdk
+[aws-cdk-rfcs]: https://github.com/aws/aws-cdk-rfcs
+[jsii]: https://github.com/aws/jsii
+
+## Roadmap FAQs
+
+**Q: How do you manage the roadmap?**
+
+A: We know that our customers are making decisions and plans based on what we
+are developing, and we want to provide the information they need to be successful. Our roadmap management tenets are:
+
+* **Be transparent** with customers about the AWS CDK team’s work in progress
+* **Listen to customers,** allowing them to participate in design decisions and to vote on and propose new AWS CDK
+  features. We will periodically re-prioritize the roadmap based on customer feedback
+* **Stay up-to-date,** or we will lose customer trust
+* **Provide the right level of detail** so customers can easily see what we’re working on at a glance, without being
+  overwhelmed by minutiae
+* **Guide the community** on what AWS CDK constructs or features to contribute without the risk of conflicting with work
+  already in progress
+
+**Q: What do the roadmap project board columns mean?**
+
+A: There are four columns on the roadmap project board:
+
+* **Researching** - We’re thinking about it, but cannot commit if, or when, we will work on items in this list.
+  This means we are still designing the feature and evaluating how it might work. This is the phase when we collect
+  customer use cases and feedback on how they want to see something implemented. There is no firm commitment to deliver
+  functionality listed in the Researching column, and there might be situations that require us to move items from the
+  roadmap back to the backlog.
+* **We’re working on it** - In progress, but further out. We have made an implied commitment to work on items in this
+  bucket, they have some level of design spec’ed out, and a developer assigned to them. Items might linger in this
+  bucket as we work through the implementation details, or scope stuff out. Think several months out until a developer
+  preview release, give or take.
+* **Developer preview** - It’s available now as a release candidate. Items will spend extended periods of time in
+  developer preview as we conduct user acceptance testing and accumulate sufficient usage to declare the API stable and
+  ready for general availability. We will only make breaking changes to developer preview modules when we need to address unforeseen use cases or issues. Not all
+  features, such as enhancements to the CDK CLI, will have a developer preview phase. In these cases the tracking issue
+  is moved directly to the Shipped bucket when released.
+* **Shipped** - It’s available now, fully supported by AWS, and we guarantee the API is stable and safe to use in
+  production.
+
+**Q: How do items on the roadmap move across the project board?**
+
+A:  The [AWS Construct Library module lifecycle
+document](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) describes how
+we graduate packages from experimental, to developer preview, to generally available.
+
+**Q: Why are there no dates on this roadmap?**
+
+A: Security and operational stability are our main priority and we will not ship a feature until these criteria are met,
+therefore we generally don’t provide specific target dates for releases.
+
+**Q: Is every feature on the roadmap?**
+
+A: The AWS Cloud Development Kit roadmap provides transparency on our priority for adding new programming languages,
+developer experience improvements, and service coverage in the AWS Construct Library. The AWS CDK toolkit and AWS
+Construct Library are such a large surface areas we are intentionally keeping the roadmap at a high-level, so not every
+CDK feature request will appear on the roadmap. Instead, the roadmap will include a tracking issue
+for each deliverable that provides a feature overview and contains links to relevant, more granular issues and pull
+requests. If you want to track the status of a specific issue or pull request, you can do so by monitoring that work
+item in the [aws-cdk] GitHub repository.
+
+**Q: What is a tracking issue?**
+
+A: We create a tracking issue for each CDK feature, AWS Construct Library module, and jsii-supported programming language. Tracking issues provide a brief summary of the feature and a consolidated view of the work scoped for the release. They include links to design documentation, implementation details, and relevant issues. Tracking issues are living documents that start from a basic template and grow more robust over time as we experiment and learn. You can easily find tracking issues by filtering on the [management/tracking label](https://github.com/aws/aws-cdk/labels/management%2Ftracking).
+
+**Q: How can I provide feedback on the roadmap or ask for more information about a feature?**
+
+A: Please open an issue!
+
+**Q: How can I request a feature be added to the roadmap?**
+
+A: Please open an issue! Community submitted issues will be tagged “feature-request” and will be reviewed by the team.
+
+**Q: Can I “+1” tracking issues and feature requests?**
+
+A: We strongly encourage you to do so, as it helps us understand which issues will have the broadest impact. You can navigate to the issue details page and add a reaction. There are six types of reactions (thumbs up “+1”, thumbs down “-1”, confused, heart, watching, laugh, and hooray) you can use to help us decide which items will benefit you most.
+
+**Q: Will you accept a pull request to the aws-cdk repo?**
+
+A: Yes! We take PRs very seriously and will review for inclusion. You can read how to contribute to the CDK [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md).

allowed-breaking-changes.txt

@@ -31,6 +31,7 @@ incompatible-argument:@aws-cdk/aws-apigateway.ProxyResource.addProxy
 incompatible-argument:@aws-cdk/aws-apigateway.Resource.addProxy
 incompatible-argument:@aws-cdk/aws-apigateway.ResourceBase.addProxy
 incompatible-argument:@aws-cdk/aws-apigateway.IResource.addProxy
+incompatible-argument:@aws-cdk/aws-apigateway.RequestAuthorizer.<initializer>
 incompatible-argument:@aws-cdk/aws-servicediscovery.Service.fromServiceAttributes
 removed:@aws-cdk/core.ConstructNode.addReference
 removed:@aws-cdk/core.ConstructNode.references

design/aws-guidelines.md

@@ -437,7 +437,7 @@ class ImportedFoo extends FooBase {
 - [ ] Metrics (`metricXxx`)
 - [ ] Events (`onXxx`)
 - [ ] Security Groups (`connections`)
-- [ ] Pipeline Actions (`addToPipline`)
+- [ ] Pipeline Actions (`addToPipeline`)
 - [ ] SNS Targets
 - [ ] `_asFooTarget`
 - [ ] TODO: other cross AWS patterns

design/cloud-assembly.md

@@ -62,7 +62,7 @@ In other words, *Logical IDs* are expected to match the following regular expres
 ```
 
 ### Droplet
-Clouds are made of Droplets. Thet are the building blocks of *Cloud Assemblies*. They model a part of the
+Clouds are made of Droplets. They are the building blocks of *Cloud Assemblies*. They model a part of the
 *cloud application* that can be deployed independently, provided its dependencies are fulfilled. Droplets are specified
 using [JSON] objects that **MUST** conform to the following schema:
 
@@ -197,7 +197,7 @@ Key   |Type    |Description
 Here is a schematic example:
 ```js
 {
-  // When this attestation doucment was created
+  // When this attestation document was created
   "timestamp": "2018-11-15T11:08:52",
   // The hashing algorithm for the attestation is SHA256
   "algorithm": "SHA256",
@@ -216,7 +216,7 @@ Here is a schematic example:
 ```
 
 Once the attestation is ready, it is digitally *signed* using the configured [PGP][RFC 4880] key. The key **MUST** be
-valid as of the `timestamp` field included in the attestation. The siganture **MUST** not be detached, and is
+valid as of the `timestamp` field included in the attestation. The signature **MUST** not be detached, and is
 **RECOMMENDED** to use the *cleartext signature framework* described in section 7 of [RFC 4880] so the attestation can
 be read by a human.
 
@@ -229,7 +229,7 @@ Deployment systems that support verifying signed *Cloud Assemblies*:
   be returned when attempting to deploy an un-signed *Cloud Assembly*.
 * **MUST** verify the integrity and authenticity of signed *Cloud Assemblies* prior to attempting to load any file
   included in it, except for `signature.asc`.
-  * An error **MUST** be raised if the *Cloud Assembly*'s integirty is not verified by the signature.
+  * An error **MUST** be raised if the *Cloud Assembly*'s integrity is not verified by the signature.
   * An error **MUST** be raised if the [PGP][RFC 4880] key has expired according to the signature timestamp.
   * An error **MUST** be raised if the [PGP][RFC 4880] key is known to have been revoked. Deployment systems **MAY**
     trust locally available information pertaining to the key's validity.
@@ -470,4 +470,4 @@ Hash: SHA256
 [ISO/IEC 21320-1:2015]: https://www.iso.org/standard/60101.html
 [JSON]: https://www.json.org
 [RFC 4880]: https://tools.ietf.org/html/rfc4880
-[ISO 8601]: https://www.iso.org/standard/40874.html
+[ISO 8601]: https://www.iso.org/standard/40874.html