terraform/backend/local
James Bardin 928e60672f context Refresh and Apply sometimes return nil
The documentation for Refresh indicates that it will always return a
valid state, but that wasn't true in the case of a graph builder error.
While this same concept wasn't documented for Apply, it was still
assumed in the terraform apply code.

Since the helper testing framework relies on the absence of a state to
determine if it can call Destroy, the Context can't can't start
returning a state in all cases. Document this, and use the State method
to fetch the correct state value after Apply.

Add a nil check to the WriteState function, so that writing a nil state
is a noop.

Make sure to init before sorting the state, to make sure we're not
attempting to sort nil values. This isn't technically needed with the
current code, but it's just safer in general.
2017-04-14 14:56:10 -04:00
..
test-fixtures
backend.go
backend_apply.go context Refresh and Apply sometimes return nil 2017-04-14 14:56:10 -04:00
backend_apply_test.go
backend_local.go
backend_plan.go
backend_plan_test.go
backend_refresh.go
backend_refresh_test.go
backend_test.go
cli.go
counthookaction_string.go
hook_count.go
hook_count_action.go
hook_count_test.go
hook_state.go
hook_state_test.go
local_test.go
testing.go