-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow printing and/or saving output vars #1209
Comments
I'm just looking at
|
So, |
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
Going to centralize on Radek's mega issue since this is fairly simple (#2460) |
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 have 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. |
It would be nice if terraform could be moving a bit towards the concept of "stacks" and sharing variables between these stacks. Inspiration here.
Module is a nice concept for code reuse, putting aside the fact that dependencies don't work well yet, it's generally not always the right solution for all problems anyway.
I'm not sure how the right API & wrapper should look like, but here's an idea:
Which already expects #1084 to be solved.
I believe it should have a special extension (
tfout
or any similar) so that if it gets generated into the same directory, it is not picked up in next run as an input.I believe it should be generating this output by default to any default location (
terraform.tfout
?) so that user doesn't have to think about passing extra option for each stack. More importantly the only way I can get to the output now is to open a (possibly giant)*.tfstate
and look foroutputs
which isn't really nice experience.This could also be helpful for #610
The text was updated successfully, but these errors were encountered: