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
The route path will no longer specify access (i.e. "/api/x" vs "/internal/x" will not have any access effect anymore)
A route must be tagged with access:{valid_access_string} to specify its intended access
Any route that isn't tagged with the access: tag will be PRIVATE by default
We will probably need to make changes to various APIs we maintain in order to account for this change in V9. As a first step, we need to index all of the API routes for the areas we maintain, along with their intended access level, and whether or not they already use the access: tag.
Acceptance criteria
The index below is filled out with all known API routes maintained by our team (@elastic/obs-ux-management-team) as of this issue writing in September 2024. Those areas are currently:
API route access is changing in V9. The main takeaways are:
access:{valid_access_string}
to specify its intended accessaccess:
tag will be PRIVATE by defaultWe will probably need to make changes to various APIs we maintain in order to account for this change in V9. As a first step, we need to index all of the API routes for the areas we maintain, along with their intended access level, and whether or not they already use the
access:
tag.Acceptance criteria
API Index
SLO
Synthetics
Uptime
RCA initiative
Currently volatile, no need to document for now, nothing here is public.
Exploratory view
No API routes.
Observability plugin
The text was updated successfully, but these errors were encountered: