Serve /schemas/ from the S3 bucket/Cloudfront too. #1229
Closed
Conversation
This file contains hidden or 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
This gives us a place outside of versioned docs to Publish Open API or JSON schemas. I removed the `NC` flag which makes it do a case-insensitve comparission as the case actually matters here, if we have a request to `/Docs` it will 404, so there's no point sending it to S3
|
Not needed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 gives us a place outside of versioned docs to Publish Open API or JSON
schemas.
I removed the
NCflag which makes it do a case-insensitve comparission asthe case actually matters here, if we have a request to
/Docsit will 404,so there's no point sending it to S3
This is #1228 but for the staging branch too