Type of the user-defined config object passed to each stage.
Sync constructor. Typed against the Amplify PipelineProps (required
stageFactory, plus the internal _sourceOverride test hatch that
@aws-blocks/pipeline consumes at runtime but omits from its public type).
Delegates entirely to the upstream Pipeline.
Type of the user-defined config object passed to each stage.
ReadonlycodeThe underlying CDK Pipelines CodePipeline instances, keyed by branch name.
ReadonlynodeThe tree node.
Returns a string representation of this construct.
Applies one or more mixins to this construct.
Mixins are applied in order. The list of constructs is captured at the
start of the call, so constructs added by a mixin will not be visited.
Use multiple with() calls if subsequent mixins should apply to added
constructs.
The mixins to apply
This construct for chaining
StaticcreateAsync factory (for an async stageFactory), typed against the Amplify
PipelineProps. Delegates to Pipeline.create.
StaticisChecks 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.
CDK Pipelines-based CI/CD pipeline construct (L3).
A named re-export of
@aws-blocks/pipeline'sPipeline, kept for API stability. It behaves identically to the upstream construct — one self-mutating CodePipeline V2 per branch, deploying to ordered stages with optional approval and bake time. Per-stage post-deploy steps (e.g. the Amplify hosting deploy) are supplied through the upstreampostStageprop rather than any Amplify-specific wrapping.Example