Update issuer configuration to allow dynamic values #144
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
Useful in cases where Doorkeeper API mode is enabled and requests are proxied from multiple hosts
|
@maxxsnake thanks, this LGTM and makes sense! 👍 I'll go ahead and merge this, and will also update the README to mention the block syntax. |
This was referenced Nov 12, 2021
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.
Proposing a small change here so that
issueraccepts a string or a block. This is useful in cases where Doorkeeper API mode is enabled and requests are proxied from multiple hosts, so that the value may be set dynamically from the resource owner and/or application. Please let me know if you have any concerns. Thanks!