mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
chore(deploy): wire self-heal env into the compose (default-off, ci.yml-scoped)
Plumb the self-healing knobs into the orchestrator service so a NAS deploy is configured without hand-editing env: both toggles default OFF (armed from Settings -> Feature Flags), the CI signal is scoped to ci.yml (RoboCo has several workflows, so the unscoped "latest completed run" would be unreliable), and PROJECT_SLUG is left for the deployment to set (which registered project IS RoboCo). Mirrored byte-identically into the untracked docker-compose.yaml the NAS uses.
This commit is contained in:
@@ -293,6 +293,17 @@ services:
|
||||
ROBOCO_EXTERNAL_PR_REQUIRE_HUMAN_CONFIRM: ${ROBOCO_EXTERNAL_PR_REQUIRE_HUMAN_CONFIRM:-true}
|
||||
# ROBOCO_EXTERNAL_PR_POLL_INTERVAL_SECONDS: "300"
|
||||
# ROBOCO_EXTERNAL_PR_AUTHOR_ALLOWLIST: '["corey"]' # empty = every external PR
|
||||
# Production self-healing ("engine 4"). RoboCo watches its OWN repo CI and,
|
||||
# when red, notifies the CEO and (with originate on) opens a PENDING fix
|
||||
# task that STOPS for the CEO's Approve-&-Start — it never self-deploys.
|
||||
# Both toggles default OFF (arm from Settings -> Feature Flags). Set
|
||||
# PROJECT_SLUG to the registered project that IS RoboCo; CI_WORKFLOW scopes
|
||||
# the signal to the real CI workflow (RoboCo has several workflows, so the
|
||||
# unscoped "latest run" would be unreliable).
|
||||
ROBOCO_SELF_HEAL_ENABLED: ${ROBOCO_SELF_HEAL_ENABLED:-false}
|
||||
ROBOCO_SELF_HEAL_ORIGINATE_ENABLED: ${ROBOCO_SELF_HEAL_ORIGINATE_ENABLED:-false}
|
||||
ROBOCO_SELF_HEAL_PROJECT_SLUG: ${ROBOCO_SELF_HEAL_PROJECT_SLUG:-}
|
||||
ROBOCO_SELF_HEAL_CI_WORKFLOW: ${ROBOCO_SELF_HEAL_CI_WORKFLOW:-ci.yml}
|
||||
volumes:
|
||||
# Docker socket - allows spawning agent containers
|
||||
- /var/run/docker.sock:/var/run/docker.sock
|
||||
|
||||
Reference in New Issue
Block a user