provider/aws: aws_vpn_gateway_route_propagation resource #15137
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a separate resource that serves a similar purpose to the
propagating_vgws
argument onaws_route_table
, but allows route propagations to be created independently of the route table, which inturn allows the VPN gateway to be created after the route table it will contribute to, possibly in a separate Terraform module.
To make this work,
propagating_vgws
onaws_route_table
is now marked asComputed
, meaning that it won't try to delete any existing propagation edges if there is no setting for it in configuration at all. This allows the user to choose whether to use the argument or the separate resource, though using both together will not work, as explained in the docs.This is a slight change in existing behavior, because previously the
aws_route_table
resource would actively remove any existing route propagation relationships if the argument was not set in config.This fixes #3424.