feat: add client and client_url support to PagerDuty Event API#6266
Open
alpar wants to merge 1 commit intokeephq:mainfrom
Open
feat: add client and client_url support to PagerDuty Event API#6266alpar wants to merge 1 commit intokeephq:mainfrom
alpar wants to merge 1 commit intokeephq:mainfrom
Conversation
Adds optional 'client' and 'client_url' parameters to _build_alert method.
These are top-level fields in PagerDuty Events API v2 that display a
'Client view in {client}' link in the PagerDuty UI.
Fixes keephq#6233
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
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.
Summary
Adds
clientandclient_urloptional parameters to PagerDuty Event API.Changes
clientandclient_urlas top-level payload fields in_build_alertmethodReference
Comparison with existing PR #6234
This PR is cleaner - it does NOT include the unrelated version bump in pyproject.toml.