You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 2: HTTP API interfaces must not implicitly include your SO-attribs
The goal is to isolate clients from direct knowledge of your SO-attribs. A change in SO-attribs may necessitate a change in one or more of our HTTP API interfaces, but this should be updated as a separate step.
The content you are editing has changed. Please copy your edits and refresh the page.
Problem
To support serverless, we need to migrate to versioned HTTP APIs as described in the doc.
Appetite: small
Solution
@elastic/uptime
The various steps of the migration are defined in the doc
Release Target: GA
Progress Tracking
Step 1: Remove dependency on public saved objects HTTP APIs
Tasks
Step 2: HTTP API interfaces must not implicitly include your SO-attribs
The goal is to isolate clients from direct knowledge of your SO-attribs. A change in SO-attribs may necessitate a change in one or more of our HTTP API interfaces, but this should be updated as a separate step.
Tasks
fields
from QuerySchema #153472Step 3: HTTP APIs have strict input validation
Tasks
Step 4: Keep HTTP APIs interfaces as “narrow” as possible
Done and covered in step 3
Step 6: Adopt the Elastic serverless HTTP API specification
None required
The text was updated successfully, but these errors were encountered: