fix: feat: make gardener and architect schedules configurable via env vars (#558)
Some checks failed
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline failed
ci/woodpecker/pr/smoke-init Pipeline was successful

This commit is contained in:
Claude 2026-04-10 10:29:56 +00:00
parent 42d4367fe1
commit 45cac8c050
3 changed files with 20 additions and 8 deletions

View file

@ -90,6 +90,8 @@ _generate_local_model_services() {
WOODPECKER_DATA_DIR: /woodpecker-data
FORGE_BOT_USER_${service_name^^}: "${forge_user}"
POLL_INTERVAL: "${poll_interval_val}"
GARDENER_INTERVAL: \${GARDENER_INTERVAL:-21600}
ARCHITECT_INTERVAL: \${ARCHITECT_INTERVAL:-21600}
depends_on:
- forgejo
- woodpecker
@ -290,6 +292,8 @@ services:
DISINTO_CONTAINER: "1"
PROJECT_REPO_ROOT: /home/agent/repos/${PROJECT_NAME:-project}
WOODPECKER_DATA_DIR: /woodpecker-data
GARDENER_INTERVAL: ${GARDENER_INTERVAL:-21600}
ARCHITECT_INTERVAL: ${ARCHITECT_INTERVAL:-21600}
# IMPORTANT: agents get explicit environment variables (forge tokens, CI tokens, config).
# Vault-only secrets (GITHUB_TOKEN, CLAWHUB_TOKEN, deploy keys) live in
# .env.vault.enc and are NEVER injected here — only the runner