ci(openapi): add openapi-validate workflow (PR #5 natural follow-up)#12
Open
estebanzimanyi wants to merge 1 commit into
Open
ci(openapi): add openapi-validate workflow (PR #5 natural follow-up)#12estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
estebanzimanyi
force-pushed
the
feat/openapi-validator-gate
branch
4 times, most recently
from
420f869 to
65b79bb
Compare
Runs the full regenerate path on every PR touching the parser, generator, meta files, or generate_openapi.py: - libclang sysroot install (matches MobilityAPI vendor-drift) - clone MobilityDB master for MEOS headers - run.py + generate_openapi.py - openapi-spec-validator against OpenAPI 3.1 - upload meos-openapi.json as an artefact Catches OpenAPI 3.1 violations the moment a generator change introduces them, instead of letting downstream consumers (MobilityAPI vendor-drift, PyMEOS-CFFI codegen, MobilityDuck binding generator) discover them later. Named as a 'natural follow-up' in PR #5's body.
estebanzimanyi
force-pushed
the
feat/openapi-validator-gate
branch
from
65b79bb to
b2fd812
Compare
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
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.
Adds a CI gate that runs the full regenerate path on every PR touching the parser, generator, meta files, or
generate_openapi.py, and validates the producedoutput/meos-openapi.jsonagainst the OpenAPI 3.1 specification withopenapi-spec-validator.Trigger
parser/**,generator/**,meta/**,generate_openapi.py,run.py,requirements.txt, or the workflow itself.master(post-merge sanity).workflow_dispatch.Behaviour
The workflow installs the same libclang sysroot dev-header set as MobilityAPI's vendor-drift workflow (so the two regenerate paths produce byte-identical catalogs), clones MobilityDB master for MEOS headers, runs
run.pythengenerate_openapi.py, and validates the projection.The generated
meos-openapi.jsonis uploaded as a workflow artefact so downstream consumers (MobilityAPI vendor-drift, PyMEOS-CFFI codegen, MobilityDuck binding generator) can pin to a specific build without re-running the generator.Dependency
Stacks on #5 (
feat/openapi-generator) — the workflow needsgenerate_openapi.pyto exist. When #5 lands, this PR's base reverts tomaster.