Split swagger.yml into separate files #185
Draft
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
OpenAPI has support for multiple files using `$ref`. This uses that to split off the partner API into separate files. To make it easy to find the files I'm nameing them exactly like the `path` in the main swagger file. There's one catch though. The cloudbuild has to be updated to include all the new files, and to not add to the pile of one-liners I'm moving the bash script into its own file. This has a caveat in that Cloud Build uses _substitutions_ instead of environment variables. The fix is easy enough, pass BRANCH_NAME as an explicit argument to the script.
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.
OpenAPI has support for multiple files using
$ref. This uses that to split off the partner API into separate files. To make it easy to find the files I'm nameing them exactly like thepathin the main swagger file.There's one catch though. The cloudbuild has to be updated to include all the new files, and to not add to the pile of one-liners I'm moving the bash script into its own file. This has a caveat in that Cloud Build uses substitutions instead of environment variables. The fix is easy enough, pass BRANCH_NAME as an explicit argument to the script.