[v6] Provide a dedicated API endpoint for app FQDN resolving #6641
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
Currently, an app's target FQDN can be obtained only using the endpoint for creating new app sessions. The OAuth-style back-and-forth redirects between the app launcher and the app itself are therefore forced to generate an unnecessary additional app session just to resolve the FQDN. The new endpoint introduced here allows to resolve such FQDNs by invoking a dedicated endpoint.
andrejtokarcik
requested review from
alex-kovoy,
klizhentas,
r0mant and
russjones
as code owners
awly
approved these changes
Apr 28, 2021
russjones
approved these changes
Apr 28, 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.
Backport of #6449.