Fleet Website - 5XX on /api/v1/microsoft-compliance-partner

[BCTBB]

💥  Actual behavior

We received a 5XX alert in help-p1 for a single failed request on /api/v1/microsoft-compliance-partner. #31506 - a similar failure, for a different endpoint, and changes were made to treat future 5XX failures as a 4XX

Nov 26 01:03:54 PM   at=info method=POST path="/api/v1/microsoft-compliance-partner" host=fleetdm.com request_id=<redacted> fwd="<redacted>" dyno=web.2 connect=0ms service=18ms status=500 bytes=21 protocol=http2.0 tls=true tls_version=tls1.3

Nov 26 01:03:54 PM   error: Sending 500 ("Server Error") response:
Nov 26 01:03:54 PM    AdapterError: Would violate uniqueness constraint-- a record already exists with conflicting value(s).
Nov 26 01:03:54 PM       at Object.fn (/app/api/controllers/microsoft-proxy/create-compliance-partner-tenant.js:45:53)
Nov 26 01:03:54 PM       at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Nov 26 01:03:54 PM   <- POST /api/v1/microsoft-compliance-partner  (17ms 500)
Nov 26 01:03:54 PM    |  error
Nov 26 01:03:54 PM    °

🛠️ To fix

If handled similar to #31506, treat future failures with the same error as a 4XX, as long as no there are no other underlying issues that lead to the alert.

🧑‍💻  Steps to reproduce

Unknown

🕯️ More info (optional)

1. Link to Alert

[eashaw]

The website will now return a 409 response if the database adapter returns a uniqueness error.

[fleet-release]

Unique records request,
Fleet's cloud city adjusts, calm.
Error, now a gust.