Skip to content

Repository secrets

Repository secrets are environment variables for one repository’s workspace, such as a package-feed token its build needs. On Colony Cloud, multi-repo workers take them in place of workspace.secret_env_vars in the configuration schema.

Go to Operations → Settings (Secrets) and open Repository secrets. Pick a repository from the selected tenant, then add, replace or delete secrets. See Secrets & keys for the rest of the page.

Only a tenant administrator can change them. A Member or an Operations-only user gets a 403. See Team and roles.

A name matches ^[A-Z_][A-Z0-9_]{0,63}$. A value is at most 2048 characters. A name on the deny-list is rejected with a field error:

  • PATH, HOME, SHELL, USER, NODE_OPTIONS, NODE_PATH, HOSTNAME, TMPDIR, PWD, NODE_EXTRA_CA_CERTS and AZURE_CONFIG_DIR.
  • Any name starting with LD_, GIT_, GH_, GITHUB_, ANTHROPIC_, CLAUDE_, OPENAI_, COLONY_ or MISE_.

Secrets are encrypted at rest. The list shows each name, its description, who last updated it and when. It never shows a value, and neither does the API. To change a secret, save a new value over it.

Each task on a multi-repo (pool) worker fetches its repository’s secrets when it starts. If Cloud can’t return them, the task isn’t claimed and the failure shows in the worker’s errors. A rotation therefore applies to the next task with no worker restart. A task for another repository on the same worker doesn’t see them. The secrets are present in setup, prebuild, checks and the agent’s environment.

Worker logs redact secret values. Don’t print a secret on purpose, because redaction can’t catch every transformed form.

EventWhen
repo_env_secret.rotatedA secret is added or replaced.
repo_env_secret.deletedA secret is deleted.
repo_env_secret.accessedA worker fetches a repository’s secrets.

Events record the repository and secret names, never values.