ReadonlyartifactsReadonlycdkReadonlycodeReadonlynodeThe tree node.
ReadonlytriggerStaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
disk are seen as independent, completely different libraries. As a
consequence, the class Construct in each copy of the constructs library
is seen as a different class, and an instance of one class will not test as
instanceof the other class. npm install will not create installations
like this, but users may manually symlink construct libraries together or
use a monorepo tool: in those cases, multiple copies of the constructs
library can be accidentally installed, and instanceof will behave
unpredictably. It is safest to avoid using instanceof, and using
this type-testing method instead.
Any object
true if x is an object created from a class which extends Construct.
StaticpipelineStaticpipeline
CDK Pipeline for Liflig.
Avoid putting multiple pipelines in a stack, since the pipeline will also keep the hosting stack up-to-date.
The pipeline is executed by writing an empty file to s3:///pipelines//trigger
Configuration files are read from S3 at the path s3:///pipelines//
For upload type "cdk-source":
cdk-source.json holding a pointer to the active CDK source that should be used. Schema:
{ bucketName: string bucketKey: string }
variables*.json which can be zero or more files with string-string map holding variables that will be written to variables.json and can be read by the the CDK application during synthesize.
For upload type "cloud-assembly":
cloud-assembly.json holding a pointer to the active CDK Cloud Assembly that should be used: Schema:
{ cloudAssemblyBucketName: string cloudAssemblyBucketKey: string }
Variables enables separation of IaC code and application code if they are not colocated in the same repository.