Provides a TypeScript API to the CDK CLI, allowing you to programmatically synthesize, deploy, and destroy CDK apps without having to worry about the idiosyncrasies of the CDK CLI.

This for illustration purposes, typically you should not hard code a stack name

    import { AwsCdkExec } from 'aws-cdk-exec';

    // illustration purposes only
    const stackName = 'myStack');
    const cdkApp = new AwsCdkExec({ appCommand: '"npx ts-node test/testapp.ts"'});
    await cdkApp.deploy(stackName);
    
    // 
    // ...  do something to your stack, such as test it.  You do integration test, right?
    // ...
    await cdkApp.destroy();

This is what you should really do, everything data driven. Perhaps deploy and destroying all in the correct order should be its own API call in the future? cdkApp.deployAll() and cdkApp.destroyAll.

Note that order is preserved as the CDK itself preserves it with list. Most apps should be destroyed in the reverse order of deployment, so that dependencies don't block destruction.

    // deploy all stacks in an app
    const cdkApp = new AwsCdkExec(/* your environment should have set up cdk.json.  see `projen` project for example */);
    const stackList = await cdkApp.list();
    const stackTemplatesDeployIds = Promise.all(stacKList.map(async el => {
      return await cdkApp.deploy(el, { asJson: true });
    }));

    // 
    // ...  do something to your stack, such as test it.  You do integration test, right?
    // ...
    
    const stackTemplatesDeployIds = Promise.all(stacKList.reverse.map(async el => {
      return await cdkApp.destroy(el, { asJson: true });
    }));

aws-cdk-exec passes any errors through as child_process.exec pattern thrown errors, so the client is expected to try/catch errors if (rarely) needed.

Typically, CDK is idempotent so there's no need to try/catch errors in a detailed manner, just exit your program, fix the problem, and run the program start to finish, and CDK will catch up where it left off. This makes your code much simpler. Idempotence good! Catch bad!

A convenient docker-compose.yml has been provided, for interactive testing/development:

docker-compose run code /bin/bash

projen is used to manage this packages files. Instead of modifying e.g. package.jason, you instead edit .projen.js and then run:

yarn run projen

All tests are Jest unit tests, and run in the standard projen manner:

yarn run test

See projen project for details... oh wait they don't have that documented yet.

For now

    yarn run build
    npm publish