Skip to Content
We are live but in Staging 🎉
BuildsAPI ReferenceBuild Secrets

Build Secrets — API Reference

Package: dodil.ignite.v1 · Service: BuildService

SaveBuildSecrets stores the credentials a build needs — registry auth, git credentials for private repos, and extra secret build args — so they can be applied automatically when a build runs.

Stored per organization, not per build. These credentials live at the org level and are applied automatically to every build in the org. This is distinct from Compute BYOI, where you reference a named SecretService slot via registry_secret_ref on the app. Build secrets have no per-build name — you save them once and they apply org-wide.

RPCHTTPstreaming
SaveBuildSecretsPUT /v1/ignite/builds/secretsunary

SaveBuildSecrets

Saves (replaces) the organization’s build credentials. All three groups are optional — send only the ones you want to set.

  • registry_credentials — map of registry URL → auth, used to push built images and to pull private base images referenced in your Dockerfile.
  • git_credentials — a PAT for cloning private git repos; auto-applied to git_source builds.
  • build_secrets — extra values exposed to the build as build args. When a build arg’s value comes from here, it is redacted to *** wherever the build record echoes args back (see Build.build_args).

Request

Field (proto)HTTP (pbjson)TypeNotes
registry_credentialsregistryCredentialsmap<string, string>Registry URL → auth, for pushing images / pulling private base images.
git_credentialsgitCredentialsGitCredentialsPAT for cloning private git repos.
build_secretsbuildSecretsmap<string, string>Extra values exposed as build args; redacted to *** in build records.

GitCredentials:

Field (proto)HTTP (pbjson)TypeNotes
usernameusernamestringGit username.
passwordpasswordstringPersonal access token (PAT).
curl -sS -X PUT "https://api.dev.dodil.io/v1/ignite/builds/secrets" \ -H "Authorization: Bearer $DODIL_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "registryCredentials": { "ghcr.io": "<base64 user:token>" }, "gitCredentials": { "username": "build-bot", "password": "ghp_xxxxxxxxxxxxxxxx" }, "buildSecrets": { "NPM_TOKEN": "npm_xxxxxxxxxxxx" } }'

Response

{ "success": true }

Once saved, git_credentials are applied automatically to git_source builds, registry_credentials to image push/pull, and any build_secrets referenced by a build arg show as *** in the resulting Build.


See also