fix: Use empty strings for metadata default values to avoid template errors #52
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
antonbabenko
approved these changes
Nov 17, 2025
antonbabenko
pushed a commit
that referenced
this pull request
Nov 17, 2025
## [2.4.2](v2.4.1...v2.4.2) (2025-11-17) ### Bug Fixes * Use empty strings for metadata default values to avoid template errors ([#52](#52)) ([2096d87](2096d87))
Member
|
This PR is included in version 2.4.2 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Motivation and Context
local.partitionis null whenvar.create = false, causing template interpolation error inaws_cloudwatch_observability.tf#50Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request