Aws-cdk: Publish public Docker image containing the CDK CLI

[clareliguori]

Some of the newer CI/CD tools out there (Bitbucket Pipelines, GitHub Actions) use Docker images as the environment for each step of the pipeline. Packaging the CDK CLI as a public Docker image would be a convenient way to integrate releasing CDK-based apps into these types of CI/CD tools.

[moofish32]

@clareliguori -- what would you think about also publishing a lambda layers artifact? I've hacked some examples together, but lambda enables a much faster execution and integration with step functions. Yes we could do this with ECS and Fargate now, but that execution was taking about 60 seconds in us-west-2 when I tested a very basic invocation. Lambda is significantly quicker.

[clareliguori]

@moofish32 I haven't seen many examples of off-the-shelf or managed CI/CD tools built on functions, so I'd personally probably prioritize container image over Lambda layer (but I'll defer to the CDK team on priority calls). Sounds like you might be rolling your own with Step Functions? Neat!

[clareliguori]

I don't think this is resolved. The ask here is for a public Docker image, for example published into the amazon DockerHub namespace. Also, the current Dockerfile is not suitable for publishing publicly: it's multiple GBs with cruft like devDependencies and the .git folder, whereas the GitHub release archives are < 200 MB.

[ScottBrenner]

Kind of related -

I made a GitHub Action for the CDK https://github.com/ScottBrenner/aws-cdk-action
.. then I realized that for people to be able to use it, it needs to have _all_ the CDK packages/dependencies installed in it, like @aws-cdk/aws-s3 etc .. and maybe even compile the code too ..

Guess it's not feasible? :sob:

[cristianrat]

@ScottBrenner Very easy to build your own. I've done just that with only the packages I need.
There are also a couple people who made them public on docker hub.