Support for PagerDuty Apps Oauth scoped token #136
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
imjaroiswebdev
force-pushed
the
app-oauth-scoped-token-support
branch
from
0662454 to
f9273cc
Compare
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.
This update brings support for using Scoped Oauth Token as mechanism to authenticate API calls to PagerDuty public APIs.
It will add two ways of setting up the http client for making the calls:
In order to communicate the library We want to use one type of token or the other, We should configure the Property
APITokenTypein client config. Which could be any of apiToken, scopedOauthToken or useAppCredentials.Additionally introduces
github.com/heimweh/go-pagerduty/persistentconfiglibrary for handling persistence of App Oauth scoped token, which can be leveraged for other Apps that make use of PagerDuty Scoped Token for authenticating API calls.