The current openapi.yaml uses external $refs to hundreds of files at http://redfish.dmtf.org/schemas/v1/*.yaml. Every consumer must:
- Fetch hundreds of external schema files over HTTP during bundling
- Handle transitive ref chains (wrapper files → versioned files → sibling schemas)
- Work around bundler differences in how cross-file local
$refs are resolved
Different bundling tools produce different results. This forces consumers to implement workarounds for their specific toolchain.
Proposal
Publish an openapi_bundled.yaml (or .json) alongside openapi.yaml in the Redfish-Publications repository with all external $refs resolved to internal #/components/schemas/ references.
This is a one-time addition to the build pipeline — likely a single redocly bundle command or equivalent — and would:
- Eliminate HTTP fetching during consumer builds
- Remove all bundler-specific edge cases
- Provide a single canonical bundled representation
- Make the spec immediately usable by any OpenAPI tool without preprocessing
The current
openapi.yamluses external$refs to hundreds of files athttp://redfish.dmtf.org/schemas/v1/*.yaml. Every consumer must:$refs are resolvedDifferent bundling tools produce different results. This forces consumers to implement workarounds for their specific toolchain.
Proposal
Publish an
openapi_bundled.yaml(or.json) alongsideopenapi.yamlin the Redfish-Publications repository with all external$refs resolved to internal#/components/schemas/references.This is a one-time addition to the build pipeline — likely a single
redocly bundlecommand or equivalent — and would: