feat(cli): serial multi-stack deploys

[DanielMSchmidt]

The goal of this PR is to make a first step towards multi-stack deployments by running each deployment after another (with no parallelism). This ships a lot of the important infrastructure (running in the correct order, handling aborts, etc) while leaving the management of multiple deployments at the same time open for a follow up PR.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/hashicorp/terraform-cdk/FvbaiDzwQ5Ma5MYCBBVezBFEw18v
✅ Preview: https://terraform-cdk-git-multi-stack-deployment-auto-bd0b32-hashicorp.vercel.app

[Deployment for c10eeaf canceled]

[jsteinich]

Synth, output, and maybe diff should support multiple stacks.

We should aim for parity with the AWS CDK with how multiple stacks are specified (https://docs.aws.amazon.com/cdk/v2/guide/cli.html#cli-stacks)

[DanielMSchmidt]

Synth, output, and maybe diff should support multiple stacks.

Yeah, we are going to do this in separate PRs for synth and output 👍 Not sure how diff should be working, if there is a dependency there might be no way to diff (if the provider requires a previously provisioned endpoint to be there for example). How do you think this should look like?

We should aim for parity with the AWS CDK with how multiple stacks are specified

Yeah agreed, will be done in a later PR :)

[jsteinich]

Not sure how diff should be working, if there is a dependency there might be no way to diff (if the provider requires a previously provisioned endpoint to be there for example). How do you think this should look like?

I would expect it to try and diff the stacks using the same dependency ordering as other places. Yes, sometimes the diff would fail, but that's not really any different than how it works in HCL.

[hashicorp-cla]

All committers have signed the CLA.

[ansgarm]

Nice work, @DanielMSchmidt 🎉

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.