fb57801dfe
We're going to allow the provider to encode whatever it wants in here, so
a provider can use whatever is most convenient for its implementation
language and to avoid some of the bugs we saw with the prior model where
the forced round-trip through JSON and back into interface{} would cause
some loss of fidelity, leading to bugs.
|
||
|---|---|---|
| .. | ||
| v1-simple.in.tfstate | ||
| v1-simple.out.tfstate | ||
| v3-grabbag.in.tfstate | ||
| v3-grabbag.out.tfstate | ||
| v3-simple.in.tfstate | ||
| v3-simple.out.tfstate | ||
| v4-simple.in.tfstate | ||
| v4-simple.out.tfstate | ||