feat: add provider selection to Opsgenie channel params#31
Open
rionthys wants to merge 1 commit into
Open
Conversation
Opsgenie channels can now target Jira Service Management, Opsgenie, or a custom endpoint. `provider` selects the alert API (required) and `endpoint` holds the URL for the custom provider. Both carry descriptions so MCP and other API clients understand the abbreviated enum values.
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.
Atlassian is retiring Opsgenie (2027-04-05) for Jira Service Management, which
serves the same alert API at a different URL. To let Opsgenie channels target
JSM, add to
OpsgenieParams:provider(required) —jsm|opsgenie|customendpoint— alert API URL for thecustomproviderBoth carry descriptions so MCP and other API clients understand the values
(
jsm= Jira Service Management, etc.).