Reload Hydra after discovery configuration changes #98
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/retire-legacy-mcp-routing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.