terraform/plans
Martin Atkins d9dfd135c6 plans: Include backend settings in plan and plan files
On the first pass here we erroneously assumed that this was redundant with
the backend settings embedded in the configuration itself. In practice,
users can override backend configuration when running "terraform init"
and so we need to record the _effective_ backend configuration.

Along with this, we also return the selected workspace name at the time
the plan was created so we'll later be able to produce a specialized error
for the situation of having the wrong workspace selected. This isn't
strictly required because we'll also check the lineage of the state, but
the error message that would result from that failure would be relatively
opaque and thus less helpful to the user.
2018-10-16 18:50:29 -07:00
..
internal/planproto plans: Include backend settings in plan and plan files 2018-10-16 18:50:29 -07:00
planfile plans: Include backend settings in plan and plan files 2018-10-16 18:50:29 -07:00
action.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
action_string.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
changes.go plans: Record provider config address in each resource change 2018-10-16 18:50:29 -07:00
changes_state.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
doc.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
dynamic_value.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
dynamic_value_test.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
plan.go plans: Include backend settings in plan and plan files 2018-10-16 18:50:29 -07:00
plan_test.go various: helpers for collecting necessary provider types 2018-10-16 18:50:29 -07:00