fix: Handle null values in dynamic for_each blocks in selection.tf #175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Replace try() with coalesce(try(..., null), {}) for all condition dynamic blocks
- Fixes "Cannot use a null value in for_each" error in issue #174
- Applied to all three backup selection resources:
- aws_backup_selection.ab_selection
- aws_backup_selection.ab_selections
- aws_backup_selection.plan_selections
- Consistent with existing pattern used elsewhere in the file
- Maintains backward compatibility while improving null handling
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Owner
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ BugBot reviewed your changes and found no bugs!
BugBot free trial expires on July 22, 2025
Learn more in the Cursor dashboard.
Was this report helpful? Give feedback by reacting with 👍 or 👎
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Fixes the "Cannot use a null value in for_each" error reported in issue #174.
Changes
try()withcoalesce(try(..., null), {})pattern for all condition dynamic blocksaws_backup_selection.ab_selectionaws_backup_selection.ab_selectionsaws_backup_selection.plan_selectionsTechnical Details
The issue occurred when
condition.value["string_equals"](and similar keys) evaluated to null, causing Terraform's for_each to fail. The fix usescoalesce()to convert null values to empty maps{}, which for_each can handle properly.Testing
Consistency
This change uses the same pattern already implemented elsewhere in the file (lines 104, 165), ensuring consistency across the codebase.
Fixes #174