Conversation
Re-vendors specs/hosted-v1.yaml and specs/dolthub-v2.yaml from ld main
(781c0ea3435).
Hosted v1 gains three Deployment endpoints and four schemas:
GET /deployments/{owner}/{deployment}/config getDeploymentConfig
GET /deployments/{owner}/{deployment}/backups listDeploymentBackups
POST /deployments/{owner}/{deployment}/disable disableDeployment
plus Backup, ConfigSetting, DeploymentConfig, and DisableAccepted. The
hand-written v1 overview picks all three up in its endpoint table, and the
long-running-work section now covers disable — it returns 202 with the
deployment in `stopping` and is polled the same way a create is — along with
the warning that disabling tears down instances and storage.
DoltHub v2 has no structural change: same 22 operations and 40 schemas. Its
diff is the RequestId header being hoisted into a shared component and error
responses being declared as application/problem+json.
That content-type change exposed a generator bug. Error bodies were looked up
under application/json only, so every error row lost its Problem schema link
the moment the declaration became application/problem+json. The hosted spec
already used problem+json, which means those rows have been blank since the
hosted docs landed. Media-type lookups now go through a jsonBody() helper that
accepts either, so both APIs link Problem again.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Re-vendors specs/hosted-v1.yaml from ld main (3654e2df4bd), which adds two
Deployment endpoints and two schemas:
POST /deployments/{owner}/{deployment}/instances addDeploymentInstance
DELETE /deployments/{owner}/{deployment}/instances/{id} deleteDeploymentInstance
plus AddInstanceRequest and InstanceDeleteAccepted. Hosted v1 is now 11
operations and 23 schemas. dolthub-v2.yaml is unchanged at this ld commit.
Both endpoints are added to the hand-written overview's endpoint table, and
Long-running work gains a paragraph for them. They return 202 like create and
disable, but unlike those there is no per-instance state field to poll, so
progress is observed through the instance list instead: an added replica is
ready when it reports a host, and a removed one is gone when it drops off the
list, which only reports instances that aren't stopped.
This is the first DELETE in either generated API doc; its badge and its
body-less curl example both render correctly.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Parameters table disappeared from the instance endpoints. The generator read only operation.parameters, but the spec now declares owner/deployment (and id) on the path item, which OpenAPI 3.1 §4.8.9 says every operation under that path inherits. Hoisting them there is the natural thing to do once a path has more than one method, which is what adding POST /instances did — so the same commit that introduced the new endpoints silently stripped the parameters off the existing GET. endpointBlock now merges the path item's parameters with the operation's, with operation-level entries overriding an inherited one of the same name and location, per the spec. The merged set also feeds the curl example, so a required query parameter declared on a path item still lands in the URL. Restores 2 parameters on listDeploymentInstances and documents 2 on addDeploymentInstance and 3 on deleteDeploymentInstance. Audited against the spec: all 11 hosted operations now render a Parameters table exactly when the spec defines parameters for them. DoltHub v2 declares none at the path-item level, so its output is byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Update both OpenAPI specs from ld main
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.
No description provided.