provider/aws: Fix source_dest_check with network_interface #14079
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.
The default value for
source_dest_check
needs to remain the same, so as not to break any backwards compatibility, however, adding a newnetwork_interface
parameter with a pre-configured network_interface that hassource_dest_check
set to false throws a diff after initial apply. Since we don't want to changesource_dest_check
to computed in order to not break sane defaults, ignore the diff thrown ifnetwork_interface
attributes are configured on an instance.Fixes: #14068