[BUG] Suppress diff for lambda target group attributes #44500
+17
−11
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.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
No changes to security controls.
Description
Fixes perpetual diff issue for Lambda target groups with stickiness, target_failover, and target_group_health attributes.
Lambda target type only supports
lambda.multi_value_headers.enabled
attribute. AWS API silently ignores stickiness, target_failover, and target_group_health configuration for Lambda target groups, but Terraform was detecting them as diffs. This means diffs will continue to appear indefinitely even after applying. Detecting diffs in the plan for changes that are not actually applied is undesirable.This change adds
DiffSuppressFunc
to these three attributes to suppress diffs whentarget_type
is lambda, using the existingsuppressIfTargetType()
helper function.Before
After
Relations
None
References