feat: hot-reload support for access controller #70
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qrayven
changed the title
wulfraem
requested changes
Jun 2, 2025
wulfraem
approved these changes
Jun 10, 2025
qrayven
force-pushed
the
qrayen/feat/reloading
branch
from
cdc3cf1 to
2f92491
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new HTTP endpoint, POST
/v1/reload_access_controller, which triggers the gas-station service to re-read its configuration file and re-instantiate the access controller with the updated rules and settings. When this endpoint is invoked, the service performs a full teardown and rebuild of the access controller component—loading the latest YAML, recompiling any embedded policies, and swapping in the new instance without requiring a process restart.Security Note
This endpoint is intentionally exposed without built-in authentication: it assumes the gas-station runs in a trusted environment. Access control for this reload operation should be enforced upstream—typically by an API gateway or HTTP proxy configured by the deployment team.
closes #61