charts/nginz: Serve swagger-ui #2466
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
akshaymankar
force-pushed
the
akshaymankar/nginz-zwagger
branch
from
3afc633
to
184cb6e
Compare
flokli
approved these changes
Jun 14, 2022
This was referenced Jul 5, 2022
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 change actually makes the swagger-ui code work by including the swagger-ui HTMLs from the private "zwagger-ui" repo into the nginz helm chart. The actually swagger-ui JS and CSS is referred to from unpkg.com. The plan is to migrate these endpoints to swagger-2.0 soon so this is just a stop gap solution.
Checklist
changelog.d.