terraform/plans/planfile
Martin Atkins 2b80df0163 backend/local: Require caller to set PlanOutBackend with PlanOutPath
We can't generate a valid plan file without a backend configuration to
write into it, but it's the responsibility of the caller (the command
package) to manage the backend configuration mechanism, so we require it
to tell us what to write here.

This feels a little strange because the backend in principle knows its
own config, but in practice the backend only knows the _processed_ version
of the config, not the raw configuration value that was used to configure
it.
2018-10-16 19:14:11 -07:00
..
testdata/test-config plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00
config_snapshot.go plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00
config_snapshot_test.go plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00
doc.go plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00
planfile_test.go plans: Retain output value changes for all outputs in memory 2018-10-16 19:14:11 -07:00
reader.go plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00
tfplan.go backend/local: Require caller to set PlanOutBackend with PlanOutPath 2018-10-16 19:14:11 -07:00
tfplan_test.go core: Fix test build for ./plans/planfile 2018-10-16 19:14:11 -07:00
writer.go plans/planfile: Reading and writing the new plan format 2018-10-16 18:50:29 -07:00