Solve invalid/incorrect URLs in Documents UI, OpenAPI/Swagger definition, and Postman collection for third-party APIs #12488
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
dakshina99
force-pushed
the
thirdparty_endpoint_issue
branch
from
0b82c4e to
ad4de10
Compare
RakhithaRR
approved these changes
Jul 15, 2024
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.
Purpose
Wrong endpoints display on the Document UI, Swagger definition, and Postman collection for third-party APIs. Production and Sandbox URLs need to be displayed on the Document UI and also need to add them into the Swagger definition
Fix
Check the current API is Advertised (Third-party) and assign the Production and Sandbox Endpoints for the server field in the Swagger definition. This has implemented for both OAS2 and OAS3.
Resolves wso2/api-manager#2601