6 Commits

Author	SHA1	Message	Date
Martin Atkins	9a398a7793	command: require resource to be in config before import ... 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.	2017-06-09 14:03:59 -07:00
Seth Vargo	7110d15f19	Add HCL syntax highlighting for everything but providers	2017-04-06 14:08:39 -04:00
Mitchell Hashimoto	f8ec7dad19	command/import: allow the -config flag to specify a config location	2016-11-09 15:09:13 -08:00
Christoph Blecker	047cdd7c09	Slight tweak to import docs to clarify state management commands (#8885)	2016-09-17 08:15:29 +01:00
Paul Stack	9a39057a4f	docs/import: Add a note to the Import section that only ENV VARs can be used atm (#8194)	2016-08-15 17:06:50 +01:00
Mitchell Hashimoto	6d9e41668f	website: basic docs on import	2016-05-18 12:57:03 -06:00