Inventory dependencies
Querysecret(secret_id) for metadata and dependent connections/Harnesses. Record readiness, enabled state, active Sessions, and cleanup responsibilities. Settle work before planned rotation. Upstream revocation remains an upstream operation; Hexagon does not automatically remove account permissions there.
Replace and revalidate
With an owner client and private environment input:A two-connection rotation example
Suppose one managed Secret is referenced by model connection A and protected HTTP connection B. Record both connection IDs and versions before changing the value. The update copies the replacement into each dependent connection’s encrypted credential, moves each to draft/disabled, clears validation and increments its version. A name-only Secret edit does not perform this dependent-connection invalidation. If A validates but B fails, enable only A after its successful check and leave B disabled. Record the partial result; do not mark the rotation complete or replay an interrupted business write to test B. After fixing B’s upstream access, validate and enable it explicitly. Use new Sessions for the changed model/protected HTTP versions and confirm real authorized access plus cleanup. For model/protected HTTP grants, authorization checks the current connection version on each subsequent request. An old grant therefore fails after rotation even if the connection is enabled again. Issuing a new grant through an old Session can returnsession_connection_changed because the Session pins the prior version. Already admitted requests are a separate case and may complete. Tool authorization recovery follows the Tool-specific flow; do not infer it from the model/HTTP grant rule.
The metadata dependency list is an inventory aid, not proof that no other work exists: its Session view is bounded and selected through pinned connection definitions. Reconcile active work and resource cleanup independently. This example is a proposed rotation exercise; it was not run against a live upstream in this review.
The dedicated connection replacement exercise replaced an inert test credential with an authorized model credential, observed the draft/disabled version change, revalidated and enabled it, and completed a new Vercel/Pi task. The Session closed, create/delete operations completed, and the test connection was deleted; the original shared connection version was unchanged. This demonstrates Hexagon connection credential replacement, not upstream account key issuance/revocation or encryption-key rotation.
Disable, delete, and registry references
Disabling does not delete the upstream account. Undeleted connection or Harness image references prevent deletion withsecret_in_use. Do not bypass this by editing database references.
Registry Secrets serve permitted image pull paths and are read for subsequent provisioning, not injected as ordinary Agent environment. Verify new pulls, private-registry capability, and existing registration references separately.