Reload Hydra after discovery configuration changes #98

Merged
binjovi-bot merged 1 commit from feat/retire-legacy-mcp-routing into trunk 2026-09-11 19:22:16 +00:00
Owner

Live verification of the preceding cleanup found that Hydra still served its old discovery document: the config is a startup-mounted file and the Deployment lacked a reload trigger. Add the existing cluster reloader annotation for hydra-config, with a regression guard. Full tests/check.sh passes. This uses the normal rolling deployment and does not change issuer, signing keys, or database state.

Live verification of the preceding cleanup found that Hydra still served its old discovery document: the config is a startup-mounted file and the Deployment lacked a reload trigger. Add the existing cluster reloader annotation for hydra-config, with a regression guard. Full tests/check.sh passes. This uses the normal rolling deployment and does not change issuer, signing keys, or database state.
Roll Hydra when its discovery configuration changes
All checks were successful
binjovi/ci Binjovi completed the frozen plan
c07ca88cf1
binjovi-bot deleted branch feat/retire-legacy-mcp-routing 2026-09-11 19:22:16 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/ory!98
No description provided.