Secrets / Opt in deliberately
Secrets follow trust.
File-backed secrets are disabled by default. When enabled, Rookrunner evaluates the event and configured allowlist before injecting a secret into a supported step context.
Enable file secrets
Start the worker with --secrets and --github-repository OWNER/NAME. Secret files live under ~/.config/rookrunner/files/OWNER/REPO/, or under the same path within $XDG_CONFIG_HOME when set. The worker option takes no secret-directory path.
Supported workflow use
Supported references are exact secrets.NAME expressions in step env and with, plus supported Bash and sh run contexts. Secret values are masked in logs and are not written into the run record. Unsupported contexts should not be assumed to work.
Default eligibility
- With no explicit allowlist entries, default-branch pushes, schedules, and manual workflow dispatches match the file-secret allowlist.
- Fork pull requests are refused by default and do not receive file secrets.
- Same-repository pull requests are subject to trust and allowlist checks; do not assume all such runs are denied or eligible.
--secret-refand--secret-pusheradd explicit allowlist matches.
The worker refuses some combinations of secrets, application credentials, and Docker socket access unless the key-directory probe passes. Keep the host, secret files, and worker configuration under operator control. See the security model for the trust boundary.