all plan --output and all up --plan options

[tongueroo]

This is a 🙋‍♂️ feature or enhancement.

• I've added tests (if it's a bug, feature or enhancement)
• I've adjusted the documentation (if it's a feature or enhancement)
• The test suite passes (run bundle exec rspec to verify this)

Summary

• value processed by expander

Using Plans

Using plan output path. You can specify an output path for the plan that contains pattern for expansion. Example:

terraspace all plan --out "plans/:MOD_NAME.plan"

You can then use this later in terraspace up:

terraspace all up --plan "plans/:MOD_NAME.plan"

Context

Closes #156

How to Test

See using plans above.

Version Changes

Patch

[tongueroo]

Released in 1.1.0

[frankabee]

@tongueroo I have currently an issue with the new terraspace all plan feature. In the logs it looks like the
terraform plan -input=false -out plans/example-stack.plan
is executed 4 times for each stack. This means, for an overall setup with 3 modules, the command is executed 12 times.

In the timestamps in the log I can see that this is not a repetition of the log itself, the timestamps differ for each execution.

I am using terraspace like this:

terraspace all plan --yes --out=plans/:MOD_NAME.plan

Using the logfiles directly from log/plan/ directory.

Version of Terraspace is 1.1.1

Can you confirm or deny this behaviour? Thanks 🌵

Small update from my side: Is it possible, that the log is ammending the files when rerun? Looks to me like that after investigating the issue.