Skip to content

fix(ci): preserve existing Kache config - #159

Merged
jmagar merged 6 commits into
mainfrom
fix/preserve-existing-kache-config-20260802
Aug 2, 2026
Merged

fix(ci): preserve existing Kache config#159
jmagar merged 6 commits into
mainfrom
fix/preserve-existing-kache-config-20260802

Conversation

@jmagar

@jmagar jmagar commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • preserve any existing non-empty Kache config on persistent/self-hosted runners
  • continue generating filesystem or local-only config on clean runner homes
  • prevent CI jobs from stripping dookie's NFS remote and daemon settings

Incident

A temporary self-hosted runner on dookie rewrote ~/.config/kache/config.toml to a 40 GiB local-only file because /home/runner/kache-remote was absent. This guard keeps host-owned configuration intact.

Validation

  • existing config path: preserved
  • empty runner home with writable farm remote: generated filesystem config
  • empty runner home without remote: generated local-only fallback

@jmagar
jmagar merged commit f721a50 into main Aug 2, 2026
18 checks passed
@jmagar
jmagar deleted the fix/preserve-existing-kache-config-20260802 branch August 2, 2026 23:26
jmagar added a commit that referenced this pull request Aug 7, 2026
This repository is public. Three internal identifiers were committed under
.github/:

  * action.yml:34  default: "https://s3.tootie.tv"      (PR #177)
  * action.yml:228 endpoint = "http://10.1.0.2:9000"    (PR #159)
  * action.yml:233 "... via Tootie MinIO"               (PR #159)
  * actionlint.yaml self-hosted-runner labels tootie/dookie

The s3-endpoint default was never reachable. The endpoint is only consumed
inside the `KACHE_S3_ACCESS_KEY && KACHE_S3_SECRET_KEY` branch, and the only
caller that supplies those keys (release.yml) also passes
`s3-endpoint: ${{ vars.KACHE_S3_ENDPOINT }}`. The org variable holds the real
value, so nothing changes.

The hardcoded 10.1.0.2 block is dead: it needs a runner with no existing
~/.config/kache/config.toml AND a ~/.aws/credentials [kache] profile. Every
self-hosted job logs "existing kache config present - leaving it alone", so
the branch never runs. Scrubbed to the RFC 5737 documentation address and the
placeholder name already used on soma main.

actionlint's tootie/dookie labels are stale: no workflow uses them; every
self-hosted job routes through a ci-pool-* label.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant