9a398a7793
Previously we encouraged users to import a resource and _then_ write the configuration block for it. This ordering creates lots of risk, since for various reasons users can end up subsequently running Terraform without any configuration in place, which then causes Terraform to want to destroy the resource that was imported. Now we invert this and require a minimal configuration block be written first. This helps ensure that the user ends up with a correlated resource config and state, protecting against any inconsistency caused by typos. This addresses #11835. |
||
|---|---|---|
| .. | ||
| backends | ||
| commands | ||
| configuration | ||
| enterprise | ||
| import | ||
| internals | ||
| modules | ||
| plugins | ||
| providers | ||
| provisioners | ||
| state | ||
| index.html.markdown | ||