Merge pull request #14646 from hashicorp/f-update-route-table-docs-note
docs/aws: add note for aws_route_table resource
This commit is contained in:
commit
fcdf494cff
|
@ -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
|
||||||
|
|
Loading…
Reference in New Issue