Data & schema semantics

x-insta-comment

`x-insta-comment` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `See x-insta-comment on awsSettings`, `due to a bug with the terraform provider openapi plugin this has to be a list in`, `No force-new since this is expected to be used in Terraform and we expect custom`, `All fields are marked as x-internal as they are all unchangeable. This model exi`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
144 occurrences
2 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 144

What its value looks like

Value shapeOccurrences
string144

Observed values

Sampled from the specifications, most frequent first.

See x-insta-comment on awsSettingsdue to a bug with the terraform provider openapi plugin this has to be a list inNo force-new since this is expected to be used in Terraform and we expect customAll fields are marked as x-internal as they are all unchangeable. This model exiSee x-insta-comment on awsSettings in AllProviderSpecificSettingsV2Null value included for backwards compatibilitySome fields are marked as x-internal as they are all unchangeable. This model exIAM Principal ARN becomes a separate resource which has its own endpoint for pro

Providers publishing it

All 1.

instaclustr

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the data & schema semantics job.