forust
7ce727bc8a
The config lived in renovate.json at the repo root while everything else Renovate-related sat under renovate/, and renovate/config.js was a second, unused source of truth. Both are gone: renovate/renovate.json is now the only config file. Because the CronJob in the cluster cannot read the repository, its ConfigMap carries an inlined copy of the config. That copy is generated, and sync-renovate-configmap.sh --check now fails the build when it drifts from the source file. The workflows also stop carrying a copy of the renovate/renovate image tag. They read it from renovate/k8s/cronjob.yaml, so the version validated in CI is the version that actually runs in the cluster. ci.yaml validates the config with renovate-config-validator, checks the generated ConfigMap, and kubeconforms the CronJob's own manifests.
20 lines
717 B
YAML
20 lines
717 B
YAML
services:
|
|
renovate:
|
|
# Kept in step with renovate/k8s/cronjob.yaml by the "renovate self-update"
|
|
# package rule in renovate/renovate.json.
|
|
image: renovate/renovate:44.115.9
|
|
container_name: renovate
|
|
restart: "no"
|
|
env_file:
|
|
- .env
|
|
environment:
|
|
RENOVATE_PLATFORM: gitea
|
|
RENOVATE_ENDPOINT: ${RENOVATE_ENDPOINT:?set RENOVATE_ENDPOINT}
|
|
RENOVATE_TOKEN: ${RENOVATE_TOKEN:?set RENOVATE_TOKEN}
|
|
RENOVATE_REPOSITORIES: ${RENOVATE_REPOSITORIES:?set RENOVATE_REPOSITORIES}
|
|
RENOVATE_CONFIG_FILE: /opt/renovate/renovate.json
|
|
RENOVATE_BASE_DIR: /tmp/renovate
|
|
LOG_LEVEL: ${LOG_LEVEL:-info}
|
|
volumes:
|
|
- ./renovate.json:/opt/renovate/renovate.json:ro
|