Skip to content

Match POST /pipelines' response and in-band states to the live API - #161

Merged
beckyconning merged 1 commit into
masterfrom
fix/pipeline-id-and-inband-states
Aug 29, 2026
Merged

Match POST /pipelines' response and in-band states to the live API#161
beckyconning merged 1 commit into
masterfrom
fix/pipeline-id-and-inband-states

Conversation

@beckyconning

Copy link
Copy Markdown
Contributor

Two documented-vs-live mismatches found while running the files quickstart against staging (2026-08-29):

  • POST /pipelines 201: the live body is a bare JSON string (the id alone); the spec promised {"id": "<string>"}. components/schemas/id is referenced only by this response, so the component now describes the live truth.
  • inband-state.state enum: the live API reports scheming, initial-writing, and initial-writing-completed — the last being the terminal state of a finished in-band initial load, which pollers need to recognize (the quickstart's status poll spun a full ten-minute bound waiting for a written that never comes).

Redocly lint clean (2 pre-existing warnings).

🤖 Generated with Claude Code

…e API

The live 201 from POST /pipelines is a bare JSON string (the id alone), not
the {id} object this spec promised; and in-band dataset status reports
scheming / initial-writing / initial-writing-completed, none of which the
enum carried — initial-writing-completed being the terminal state of a
finished in-band initial load. Both verified against staging 2026-08-29
while live-testing the files quickstart.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@beckyconning
beckyconning merged commit e918cb7 into master Aug 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants