Fix team_routing_rules notify id selector#84
Open
diraol wants to merge 2 commits intocloudposse:mainfrom
Open
Conversation
diraol
force-pushed
the
dro/fix_notification_rules
branch
from
ef7a4d7 to
6a341c6
Compare
diraol
force-pushed
the
dro/fix_notification_rules
branch
from
6a341c6 to
e9d735b
Compare
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
1 participant
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.
what
the routing rule notify block accepts multiple types, but was coded to work with only escalation. I'm implementing the logic process for other types.
why
That's what Opsgenie API accepts.
references