Currently we are using a URL identifier for our OpenSLO Schemas in this format:
The JSONSchema tooling supports importing schemas referenced by their ID when that ID is a URL; which is why we've chosen to use this ID format. However, in order to make that possible, we need to actually serve the schema documents at that URL. I expect this could be done in one of two ways:
- dynamic proxying of the raw content from the Github Repo
- bake in the documents through the build process to be served directly
Currently we are using a URL identifier for our OpenSLO Schemas in this format:
The JSONSchema tooling supports importing schemas referenced by their ID when that ID is a URL; which is why we've chosen to use this ID format. However, in order to make that possible, we need to actually serve the schema documents at that URL. I expect this could be done in one of two ways: