feat(cli-lib): experimental support for programatic CLI api

[mrgrain]

---

All Submissions:

• Have you followed the guidelines in our Contributing guide?

Adding new Unconventional Dependencies:

• This PR adds new unconventional dependencies following the process described here

New Features

• Have you added the new feature to an integration test?
  • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

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

[gitpod-io]

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

[rix0rrr]

I trust that this works in the working copy... I don't fully trust that this works after publishing to NPM, based on trickery and #$%*ery we do to the CLI build before we publish.

Does it?

[mrgrain]

Yes it does work. This minimal example can be run in a shell:

npm install aws-cdk 
node -e "const { cli } = require('aws-cdk/lib'); cli()"

cli is the existing export. I have no reason to believe exec would behave any different. However it's tricky to proof with the current build system.

Maybe doing the code swap first would be better?

[rix0rrr]

Should we change the package name to something more along the lines of cdk-cli-lib ?

(not strictly that, but something in that vein?)

Ultimately, I'd think the goal would be for all code to live here and the dependency arrow to be reversed, right?

[mrgrain]

Should we change the package name to something more along the lines of cdk-cli-lib
(not strictly that, but something in that vein?)

Yes, I wanted to ask for feedback here. Do we have rules for when we use the @aws-cdk prefix and when not?
I could see @aws-cdk/cli-lib

Ultimately, I'd think the goal would be for all code to live here and the dependency arrow to be reversed, right?

That's 100% right.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ CLI code has changed. A maintainer must run the code through the testing pipeline (git fetch origin pull/22790/head && git push -f origin FETCH_HEAD:test-main-pipeline), then add the 'pr-linter/cli-integ-tested' label when the pipeline succeeds.

PRs must pass status checks before we can provide a meaningful review.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 96c3029
• Result: SUCCEEDED
• Build Logs (available for 30 days)

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

[mrgrain]

Closed in favor of #22836