IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs/aws: add note for aws_route_table resource

Browse Source
This commit is contained in:
Jake Champlin 2017-05-18 17:12:11 -04:00
parent 208199a554
commit b38210c597
No known key found for this signature in database
GPG Key ID: DC31F41958EF4AC2
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/docs/providers/aws/r/route_table.html.markdown
View File

@ -16,6 +16,12 @@ defined in-line. At this time you cannot use a Route Table with in-line routes
in conjunction with any Route resources. Doing so will cause in conjunction with any Route resources. Doing so will cause
a conflict of rule settings and will overwrite rules. a conflict of rule settings and will overwrite rules.
~> **NOTE on `gateway_id` and `nat_gateway_id`:** The AWS API is very foregiving with these two
attributes and the `aws_route_table` resource can be created with a NAT ID specified as a Gateway ID attribute.
This _will_ lead to a permanent diff between your configuration and statefile, as the API returns the correct
parameters in the returned route table. If you're experiencing constant diffs in your `aws_route_table` resources,
the first thing to check is whether or not you're specifying a NAT ID instead of a Gateway ID, or vice-versa.
## Example usage with tags: ## Example usage with tags:
```hcl ```hcl
@ -76,4 +82,4 @@ Route Tables can be imported using the `route table id`, e.g.
``` ```
$ terraform import aws_route_table.public_rt rtb-22574640 $ terraform import aws_route_table.public_rt rtb-22574640
``` ```