[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-05-19-renamed-and-changed-required-fields-in-databrickszerobus":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"datadog-v2-openapi","Datadog API v2","datadog","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FDataDog\u002Fdatadog-api-client-typescript\u002Fmaster\u002F.generator\u002Fschemas\u002Fv2\u002Fopenapi.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KRZM0R4H5XW836Q17V1BWQ9P","2026-05-19-renamed-and-changed-required-fields-in-databrickszerobus","Breaking","Renamed and changed required fields in DatabricksZerobus destination schema","Two required fields in the **ObservabilityPipelineDatabricksZerobusDestination** schema were renamed and are no longer required: `ingestion_endpoint` → `ingestion_endpoint_key` and `unity_catalog_endpoint` → `unity_catalog_endpoint_key`. The new fields take an environment variable name or secret identifier rather than a raw URL, and both have been removed from the `required` array. Clients sending the old field names will have those values silently ignored, and any code reading those fields from responses will break.","2026-05-19T08:00:44.177Z"]