[UbsUx][APM] Delete "Agent Configuration" API failing on localhost

[miloszmarcinkowski]

The API fails when trying to delete Agent Configuration in APM settings.

Failing API: DELETE /api/apm/settings/agent-configuration 2023-10-31

The currently running edge-oblt instance (commit: 10ec2041) doesn't have that issue. However, it doesn't help when reverting to 10ec2041 on localhost.

It looks like body parameter schema is causing bad request, but we don't know why does it work on cloud instance.

AC:

• investigate why API is failing on localhost and provide a fix

---

400 bad request examples:

Edge-oblt working example:

Working example when removed schema validation for body parameter:

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[bryce-b]

Oddly enough, this feature still works on edge-lite (f51481d) but not locally. I'll continue trying to figure out why this is.

It seems edge and edge-lite are currently running older revisions than this ticket initially tested on? 10ec204 is Oct 21st, and edge/edge-lite are running a Sept 7th revision for kibana.

[miloszmarcinkowski]

Oddly enough, this feature still works on edge-lite (f51481d) but not locally. I'll continue trying to figure out why this is.

It seems edge and edge-lite are currently running older revisions than this ticket initially tested on? 10ec204 is Oct 21st, and edge/edge-lite are running a Sept 7th revision for kibana.

@bryce-b Thank you for picking it up. I was checking https://edge-oblt.kb.us-west2.gcp.elastic-cloud.com edge-oblt instance, which runs d70e01aa (Oct 28th) revision. I check commit hash here https://edge-oblt.kb.us-west2.gcp.elastic-cloud.com/status. Which edge-olbt instance did you try?

[bryce-b]

I was using the same instance, but I clicked on the "version-info" link at the top to get the hash. which goes to this page : https://studious-disco-k66oojq.pages.github.io/edge-oblt/

I tried running a couple of different versions of kibana & ES from these earlier version to current, and the issue reproduces on all of them. Very odd to see this reproduce locally, but not on the cloud instance. I'm going to try spinning up some cloud instances to see if it reproduces there.

[bryce-b]

8.16 on cloud works fine.

[bryce-b]

I opted to move the parameters into the query, hopefully that is acceptable.
#200281

[bryce-b]

root cause: #200722

[cauemarcondes]

We can close this one now.