feat: Developer Preview of CDK Pipelines

[rix0rrr]

Adds an initial, Developer Preview version of CDK Pipelines, a
higher-level construct library to make it easy to set up CI/CD
pipelines for CDK apps.

Resolves aws/aws-cdk-rfcs#49.

---

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

[eladb]

Initial comments on readme

[eladb]

Reiterating my comment from the previous PR: can we add a CLI switch that will enable this and the bootstrap v2 in a less cumbersome way?

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: ac15d93
• Result: SUCCEEDED
• Build Logs (available for 30 days)

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

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[polothy]

Is it possible to use this feature where the CDK Application lives in one git repository, but its Pipeline lives in another git repository? Sort of like a pipeline factory, make pipelines for various projects.

[eladb]

Is it possible to use this feature where the CDK Application lives in one git repository, but its Pipeline lives in another git repository? Sort of like a pipeline factory, make pipelines for various projects.

My recommendation would be to define your pipeline factory as a construct library and publish it. Then all apps can import and use.

[ahammond]

@polothy do you mean having two cdk applications in two separate repos, one which deploys the service and another which deploys the pipeline? Having common code abstracted to a shared library makes perfect sense, but seem orthogonal to this question.

[JeremyJonas]

installCommand command is not overridable, should be as follows... as this is passing options.synthCommand to installCommand

installCommand: options.installCommand ?? 'yarn install --frozen-lockfile',

[eladb]

@JeremyJonas Can you please raise an issue about this? Closed PRs are not ideal for tracking :-)

[polothy]

do you mean having two cdk applications in two separate repos, one which deploys the service and another which deploys the pipeline?

Yes, that's exactly right.

My recommendation would be to define your pipeline factory as a construct library and publish it. Then all apps can import and use.

That's what I saw as well, just wanted to confirm. So, I wouldn't be able to use the new pipeline stuff, but I would like to extract the cdk-assets work so we can provision a pipeline that can publish all the assets for the project. Having trouble finding the docs on how I would do that. In addition, the new bootstrapping seems to share a deployment role (defaults to admin permissions), is there a way to swap in other CFN deployment roles? The S3 bucket decrypt part has me worried, but maybe CFN runs as root? So, it could decrypt assets in S3?