Repository navigation
Hayhooks 2.2.0 adds a switch to disable runtime deployment while keeping pipelines loaded at startup available for execution. #284
Highlights
- Set
HAYHOOKS_RUNTIME_DEPLOY_ENABLED=falseto disable runtime deploy and undeploy through HTTP, CLI, and MCP without enabling durable mode. - Disabled HTTP deployment routes return
404. MCP omits thedeploy_pipelineandundeploy_pipelinetools and rejects direct calls to them. - Pipelines still load from
HAYHOOKS_PIPELINES_DIRat startup and remain executable. - Updated installation and production guides, with terminal dashboard screenshots and corrected examples. #276 #277
Get started
pip install --upgrade "hayhooks==2.2.0"
export HAYHOOKS_PIPELINES_DIR=/app/pipelines
export HAYHOOKS_RUNTIME_DEPLOY_ENABLED=false
hayhooks runConfiguration and behavior
- Runtime deployment remains enabled by default for compatibility. Restart the server after changing the setting.
- Durable mode always disables runtime deployment, regardless of this setting.
- Runtime deployment accepts executable code with the server process's privileges. When enabled, restrict deployment access to trusted operators through authentication or network controls.
- Disabling runtime deployment does not authenticate pipeline execution endpoints. Existing authentication and network controls remain necessary.
See the runtime deployment setting and production guide.