Feature proposal: Workspaces

[ChrisLahaye]

• I'm submitting a ...

  • 🪲 bug report
  • 🚀 feature request
  • 📚 construct library gap
  • ☎️ security issue or vulnerability => Please see policy
  • ❓ support request => Please see note at the top of this template.

• What is the current behavior?
  When I deploy I need to state every stack explicitly. I have multiple stacks and environments, so I need to be really careful that I included every stack and that each stack is of the correct environment.

• What is the expected behavior (or behavior of feature suggested)?
  When I deploy I want to state the name of an encapsulation of multiple stacks. Terraform for example has the concept of workspaces. The CDK should ease working with multiple stacks and environments. An option would be for example to parse a yaml file containing named groups of stacks, also allowing assertions on AWS account.

• What is the motivation / use case for changing the behavior or adding this feature?
  Improving user experience, eliminating user error

[eladb]

This is a very interesting idea. I am transferring this to the RFC repo. Please follow the RFC Repo README in order to submit this as an RFC.