Add support for optional conditions in rules#180
Merged
SazniMohamed merged 1 commit intowso2:mainfrom Sep 2, 2025
Merged
Conversation
SazniMohamed
changed the title
Migara-Pramod
approved these changes
Sep 2, 2025
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
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
Refactored the conditions block in azurerm_cdn_frontdoor_rule to be fully dynamic, so it is only created when each.value.conditions contains entries.
Updated all nested dynamic condition blocks (e.g., remote_address_condition, url_path_condition, request_header_condition, etc.) to reference conditions.value instead of conditions to fix Terraform type errors.
Prevents Terraform from generating empty conditions {} blocks when no conditions are provided.
Improves state management and avoids unnecessary API updates for rules without conditions.