08ba58c8c8
Terraform's design assumes that each remote object in Terraform's care is bound to one resource instance and one alone. If the same object is bound to multiple instances then confusing behavior will often result, such as two resource configurations competing to update a single object, or objects being "left behind" when all existing Terraform deployments are destroyed. This assumption was previously only implied, though. This change is an attempt to be more explicit about it, although these are additions to some older documentation sections that have not been revised for some time and so this is just a best effort to make this information discoverable without getting drawn into a full-on reorganization of these sections. While revising this there were some particular oddities that I decided to revise while I was there, but I'll leave a fuller revision of this older content for a later commit when we have more time to review it in greater detail. |
||
|---|---|---|
| .. | ||
| environments.html.md | ||
| import.html.md | ||
| index.html.md | ||
| locking.html.md | ||
| purpose.html.md | ||
| remote.html.md | ||
| sensitive-data.html.md | ||
| workspaces.html.md | ||