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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_monitor_action_group
- fix tests and doc ofitsm_receiver
#18190azurerm_monitor_action_group
- fix tests and doc ofitsm_receiver
#18190Changes from all commits
216c195
adfae97
ccbc313
4e975c3
464c33d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we include Azure/azure-rest-api-specs#20488 in these workarounds here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From TC, this
ticket_configuration = "{}"
is still OK in July but recently Service has changed API behavior (may change again in the future). And from further test, I find the"{\"PayloadRevision\":0,\"WorkItemType\":\"Incident\"}
can work well, these two are the required keys.I think it's better to note this in the doc instead of checking in the create/update (it's too strict to check certain keys in json). And I will also include the issue in code comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@teowa - the user may or may not read the docs. Unless there is going to be a fix by the service team in the near term can we place put in a check to work around this bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added checks of the JSON blob contains
PayloadRevision
andWorkItemType
in create/update method.