Closed Bug 1462364 Opened 7 years ago Closed 7 years ago

serve schemas and references somewhere

Categories

(Taskcluster :: Services, enhancement, P4)

Product:
Taskcluster
Component:
Services
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1465769

People

(Reporter: dustin, Unassigned)

Details

At present, we are still generating schemas and references, but only using them to generate docs. They should be served at the URLs generated by tc-lib-urls. For the moment, the easiest fix may be to include them in the docs service, and just make multiple Ingress paths for /docs, /schemas, and /references. We also need to think about some of the common schemas: api-reference.json and exchanges-reference.json. Those are currently embedded in taskcluster-lib-api and pulse-publisher, respectively, and were once upon a time manually uploaded to S3. Maybe we could just copy those into the docs repository? Or do something fancy with the cluster build process?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Component: Redeployability → Services
You need to log in before you can comment on or make changes to this bug.