resource/aws_dx_lag: Deprecate number_of_connections #3367
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 to address the following test failures:
The story is that AWS provisions connections & associations automatically per
number_of_connections
(as it's passed to the API). This makes further management of connections tricky because any new non-default connection created viaaws_dx_connection_association
will cause Amazon to bumpnumber_of_connections
and cause drift as the number of connections no longer matches the initial number.Unfortunately there's no way to avoid automated provisioning as
NumberOfConnections
is a required field in the API and has to be> 0
. For that reason I decided to apply similar approach we already apply in some other resources (e.g. route table) and that is to plan removal of these default connections & associations.I didn't implement that as part of this PR though, because that would be a breaking change. The goal is to inform the user about how we're going to tackle it going forward and avoid the drift for now.
Test results