Changelog
0.20.0 (2018-12-13)
addToPipeline
method to IRepository. (#1329) (c4a9b74)haveResource
can cause tests to
fail. If allowing extension of the expected values is the intended behavior, you can
switch to the haveResourceLike
matcher instead, which exposes the previous
behavior.Changelog
0.19.0 (2018-12-04)
ecr.RepositoryRef
has been replaced by ecr.IRepository
, which
means that RepositoryRef.import
is now Repository.import
. Futhermore, the CDK
Toolkit must also be upgraded since the docker asset protocol was modified.
IRepository.grantUseImage
was renamed to IRepository.grantPull
.addBuildToPipeline
was renamed to addToPipeline
and addTestToPipeline
was renamed to addPipelineToTest
in order to align
with naming conventions.CloudFormationCapabilities.IAM
renamed to
CloudFormation.AnonymousIAM
and PipelineCloudFormationDeployActionProps.capabilities?: CloudFormationCapabilities[]
has been changed to
PipelineCloudFormationDeployActionProps.capabilities?: CloudFormationCapabilities
no longer an array.
PipelineCloudFormationDeployActionProps.fullPermissions?:
has been
renamed to PipelineCloudFormationDeployActionProps.adminPermissions:
and is required instead of optional.<a name="0.18.1"></a>
Changelog
0.18.0 (2018-11-19)
cdk bootstrap
output (#1176) (b83fe85)targetGroup.listenerDependency()
has been renamed to targetGroup.loadBalancerDependency()
.Changelog
0.17.0 (2018-11-14)
addToPipeline
method to Deployment Group. (#1166) (bdbeb7c)DockerHub.image()
to reference docker hub images, use ContainerImage.fromDockerHub()
instead.Changelog
0.16.0 (2018-11-12)
Changelog
0.15.0 (2018-11-06)
js-yaml
to yaml
(#1092) (0b132b5)securityGroup
to securityGroups
(an array of security group objects).The schema now looks like this:
applets:
MyApplet:
type: ./my-applet-file
properties:
property1: value
...
By starting an applet specifier with npm://, applet modules can directly be referenced in NPM. You can include a version specifier (@1.2.3) to reference specific versions.
queue.grantReceiveMessages
has been removed. It is unlikely that this would be sufficient to interact with a queue. Alternatively you can use queue.grantConsumeMessages
or queue.grant('sqs:ReceiveMessage')
if there's a need to only grant this action.