Description

At the moment it is only possible to initialize a codecommit repo via the underlying CfnRepository and by orchestrating the asset deployment on one's own.

Implementing it on one's own leads to bugs, such as #16958.

The heavy lifting of this action should be done by the L2 Repository construct instead.

Use Case

This feature would be neat to provide a "self-unpacking" stack with cdk-pipelines on the first deploy.
At the moment the flow of CDK pipelines requires me to init a code source (like Codecommit) first (or push content via git to it once created via CDK) and keep it in sync with my local version while deploying first time, as otherwise my pipeline would inevitably fail.

It might also be great for a variety of other usecases, such as rolling out a baseline of code into diverse repos to allow teams to utilize proven foundations.

Proposed Solution

Extend the Repository construct to take an asset as construct parameter, deploy it via CDK assets and setup permissions etc.

Other information

No response

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change