terraform/website/source
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
..
assets Update news section with YAML data file (#14612) 2017-05-18 18:49:52 +03:00
docs command: require resource to be in config before import 2017-06-09 14:03:59 -07:00
guides fix custom providers snippets (#14806) 2017-05-24 20:11:00 +01:00
intro Url to aws-two-tier example changed. (#15045) 2017-06-05 00:21:24 +03:00
layouts website: Initial docs for the new "providers" subcommand 2017-06-09 14:03:59 -07:00
upgrade-guides [docs] fix paramater name to disable locking for S3 backend (#14911) 2017-05-29 21:17:11 +01:00
404.html.md Update basic scaffolding 2017-04-06 14:08:37 -04:00
android-manifest.json.erb Add favicons 2017-04-06 14:08:40 -04:00
community.html.erb docs/community: Fix Radek's bio (#14706) 2017-05-22 09:51:09 +02:00
downloads.html.erb Update basic scaffolding 2017-04-06 14:08:37 -04:00
favicon.ico Add favicons 2017-04-06 14:08:40 -04:00
index.html.erb Update news section with YAML data file (#14612) 2017-05-18 18:49:52 +03:00
microsoft-tile.xml.builder Add favicons 2017-04-06 14:08:40 -04:00
robots.txt
security.html.erb
sitemap.xml.builder