Open criamico opened 10 months ago
Pinging @elastic/fleet (Team:Fleet)
@criamico Does this affect non-Fleet Kibana APIs that are requested in Dev Tools? If so, would it better to make a change in how Dev Tools handles Kibana APIs?
@jen-huang yes this is a general thing with dev tools. I opened this ticket based on this one, but I agree it would be better to solve it globally. I think that it was done already for public endpoints but not for internal ones.
Pinging @elastic/platform-deployment-management (Team:Deployment Management)
Thanks @criamico. I'm kicking this suggestion over to the team that owns Dev Tools (cc @alisonelizabeth).
This looks similar to: https://github.com/elastic/kibana/issues/160801
Pinging @elastic/kibana-management (Team:Kibana Management)
Kibana dev tools currently don't allow specifying headers for internal endpoints.
We've had some SDHs where the customer needed to run some internal endpoints but they ran into this issue and had to use curl instead. Let's add a querystring parameter to the internal endpoints that can benefit from it.
One example is
reset_preconfigured_agent_policies
: