Refactor: alert suppression rule block #378
Merged
Conversation
This file contains 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
more straightforward and clear than an ARM template
angela-tran
approved these changes
Dec 6, 2023
There was a problem hiding this comment.
I checked that these attributes are in azurerm 3.28.0 (the version we have in our lock file). This looks good to me 👍
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.
Redefine directly in a Terraform block, which is more straightforward and clear than the ARM template.
Reference:
azurerm_monitor_alert_processing_rule_suppressionThe
scopehere is set directly to the ID of the healthcheck alert, hence this suppression rule targets only that single resource. Thus we do not need any of the filtering for e.g.target_resource_type.Closes #356