feat(pipelines): changes needed to support other engines

[eladb]

This PR includes changes needed in the Pipelines library that can help with implementation of other pipeline engines. Namely, these changes were identified during work to implement a GitHub workflows engine.

1. Add support in PipelineStructure for publishing the CFN template of a stack to the assets bucket. This is enabled by setting publishTemplate: true.
2. Add support in PipelineStructure for omitting the "prepare" step in case the engine only wants a single step for each stack deployment. This is enabled by setting prepareStep: false.
3. Add graphNode.uniqueId which returns a graph-wide unique ID of the node.
4. Add graphNode.allDeps which returns a union of the node's dependencies and the dependencies of all its parents.
5. Renamed PipelineStructure to PipelineGraph.

Additionally, in order to allow engine providers to leverage these helpers, I've moved all these types under lib/helpers-internal so they can be imported through a barrel import: import { PipelineGraph } from '@aws-cdk/pipelines/helpers-internal'.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[rix0rrr]

Add support in PipelineStructure for publishing the CFN template of a stack to the assets bucket. This is enabled by setting publishTemplate: true.

Wait up -- you shouldn't need to do this. The DefaultSynthesizer already adds the stack template as an asset, and so it will be in the asset manifest and be uploaded as part of the regular asset publishing step.

[rix0rrr]

Consider if we want to move this from "test" to a public API (maybe with a Beta1 suffix).

If we want to do this properly we should be able to publish it as a plugin package on NPM, no? (That would prove that other people would be able to do the same)

[rix0rrr]

Where do you need CreateStack again?

[eladb]

Add support in PipelineStructure for publishing the CFN template of a stack to the assets bucket. This is enabled by setting publishTemplate: true.

Wait up -- you shouldn't need to do this. The DefaultSynthesizer already adds the stack template as an asset, and so it will be in the asset manifest and be uploaded as part of the regular asset publishing step.

This is about considering the template asset in the pipeline graph (not about adding another asset to the assembly). Without this, the PipelineStructure class used to simply filter out this asset.

[eladb]

Where do you need CreateStack again?

It's needed by the GitHub action I am using.

[eladb]

Consider if we want to move this from "test" to a public API (maybe with a Beta1 suffix).

If we want to do this properly we should be able to publish it as a plugin package on NPM, no? (That would prove that other people would be able to do the same)

Good point. Definitely doable. I guess I can extract this already to a separate package.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
• Commit ID: c401381
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository