Deploy all stack in project...or not?

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave “+1” or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

In Classic CDK I can execute this command:

cdk deploy \* That deploy all stacks in the project.

So I try the same with cdktf: cdktf deploy \* and cdktf deploy * but maybe is not intended to work in this way.

So my question, and my feature request:

• With this deploy function I understand that cdktf standard is have one stack with all the resources inside that, is correct? If not, how is intended to work? What would be the standard for organizing the project? Because usually I divide my project in different stacks that rapresent different part of project and the stacks can be many and linked together by refs! So deploy only single stacks becomes a problem with this method.
• Is a planned functionality or cdktf have made a different choice?

References

No references.

Thanks!

[DanielMSchmidt]

Yeah exactly

[github-actions[bot]]

I’m going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.