94463894ec
website: "map" a real resource to configuration, not "attach" ( #17912 )
...
In the terraform state documentation the verb "map" is widely used to
describe the relationship between an item in the state and in the real world
whereas the verb "attach" is not used anywhere.
2019-03-22 16:10:44 -07:00
5576b889ab
docs/import: Remove out of date listing of importable resources and note where to find the information
2018-02-14 12:02:45 -05:00
52f6abf47b
Document aws_route53_record importable ( #17306 )
...
See https://github.com/hashicorp/terraform-website/issues/20
2018-02-13 14:07:05 -06:00
ec2281106f
Adding documentation for all supported imports in the Heroku provider ( #16312 )
2017-11-06 16:57:57 +00:00
dceecdc047
website: dyn_record can now be imported
...
Importable as of terraform-providers/terraform-provider-dyn#19 .
2017-10-26 12:03:24 -07:00
da0aec1b32
website: attempt to clarify "terraform import" usage docs
...
Based on feedback from #15569 that the previous example was too abstract
and did not give enough context about what each of the different arguments
mean and how they generalize to other resource types.
2017-07-18 16:35:14 -07:00
6f62c0c660
Add google_compute_backend_service to imports ( #15275 )
2017-06-26 17:34:17 +03:00
c80a21610d
provider/google: SQL Database Importability ( #15372 )
...
Add `google_sql_database` and `google_sql_database_instance` to Importability page.
@danawillow
https://github.com/terraform-providers/terraform-provider-google/pull/11
https://github.com/terraform-providers/terraform-provider-google/pull/12
2017-06-23 12:15:17 +01:00
7ed70bb00e
website: new filesystem layout for core/provider split
...
This repo now contains only the core docs, with other content moving elsewhere.
2017-06-13 11:25:32 -07:00
Vangelis Katsikaros