@aws-cdk/aws-directoryservice
Advanced tools
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.Changelog
0.14.0 (2018-10-26)
IMPORTANT NOTE: when upgrading to this version of the CDK framework, you must also upgrade your installation the CDK Toolkit to the matching version:
$ npm i -g aws-cdk
$ cdk --version
0.14.0 (build ...)
addReadAutoScaling()
, call autoScaleReadCapacity()
, and similar for write scaling.XxxName
properties back into Name
. These will match the CloudFormation property names.aws-cdk
toolkit when upgrading to this version, or context providers will cease to work. All existing cached context values in cdk.json
will be invalidated and refreshed.Changelog
0.13.0 (2018-10-19)
proxy: false
and construct more complex resource paths yourself.lambda.InlineJavaScriptLambda
is no longer supported. Use lambda.Code.inline
instead; lambda.Runtime.NodeJS43Edge
runtime is removed. CloudFront docs stipulate that you should use node6.10 or node8.10. It is always possible to use any value by instantiating a lambda.Runtime
object.Changelog
0.12.0 (2018-10-12)
IMPORTANT NOTE: This release includes a fix for a bug that would make the toolkit unusable for multi-stack applications. In order to benefit from this fix, a globally installed CDK toolkit must also be updated:
$ npm i -g aws-cdk
$ cdk --version
0.12.0 (build ...)
Like always, you will also need to update your project's library versions:
Language | Update?
--------------------------- | ------------------------------------------------------------------------------------------------------------------
JavaScript/TypeScript (npm) | npx npm-check-updates -u
Java (maven) | mvn versions:use-latest-versions
.NET (NuGet) | nuget update
aws-codepipeline: this commit contains the following breaking changes:
Previously, we always required customers to explicitly name the output artifacts the Actions used in the Pipeline, and to explicitly "wire together" the outputs of one Action as inputs to another. With this change, the CodePipeline Construct generates artifact names, if the customer didn't provide one explicitly, and tries to find the first available output artifact to use as input to a newly created Action that needs it, thus turning both the input and output artifacts from required to optional properties.