History

Connection health checks (liveness) with OpenAPI backing

A connection can declare one authenticated probe operation that answers "is this credential still alive?". Core owns the vocabulary (HealthStatus, HealthCheckSpec, HealthCheckResult, HealthCheckCandidate) and dispatch (integrations.healthCheck.{get,candidates,set}, connections.{checkHealth, validate}); the OpenAPI plugin implements the probe against its stored operation bindings, ranking candidates non-destructive-first. The UI gets a status dot + Check now per connection, a health-check editor sheet, and a validate-the-key-first step in the Add Connection modal.

Rhys Sullivan committed 4 months ago

Commit 26ed9a61 parent e39dbcf30 files · +2736 −43Browse files

Showing the changes to scripts (1 of 30 files). Show all

Unified · Split

scripts/oxlint-plugin-executor/rules/require-reactivity-keys.js+4−0
@@ -17,6 +17,10 @@ const readOnlyMutations = new Set([ · 16 unmodified lines
17 "resolveSecret",17 "resolveSecret",
18 "detectSource",18 "detectSource",
19 "getDomainVerificationLink",19 "getDomainVerificationLink",
20 // Health-check probes: they hit the live upstream and return a result, but
21 // persist nothing, so there is no cached query for them to invalidate.
22 "validateConnection",
23 "checkConnectionHealth",
20]);24]);
21 25
22export default {26export default {

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t