Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Why build all stacks when not running terraspace all...? #223

Closed
ghost opened this issue Mar 14, 2022 · 1 comment
Closed

Why build all stacks when not running terraspace all...? #223

ghost opened this issue Mar 14, 2022 · 1 comment
Labels
question Further information is requested

Comments

@ghost
Copy link

ghost commented Mar 14, 2022

Currently, TS builds all dependency stacks when running normal single-stack commands, e.g. terraspace build some_stack, terraspace plan some_stack etc. If you have a complex environment, this leads to pretty long run times when deploying a single stack - much longer than running pure Terraform - and I'm not really clear on the reason for it given that the dependency stacks don't ultimately seem to be used at all (templated output() values are resolved from the dependency's statefile which is entirely independent).

Was wondering if there was a reason for this. Otherwise, would it make sense to change the default include_stacks behaviour for Builder to :root_only?

@ghost ghost added the question Further information is requested label Mar 14, 2022
@tongueroo
Copy link
Contributor

tongueroo commented Mar 14, 2022

See #199 and #215

In short, on a fresh clean machine, there would be issues. Unsure if there’s another approach. Will consider PRs for improvements. No sweat either way of course.

Also, please use the Terraspace forums for questions. 🎊Thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant