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_refon the app. Build secrets have no per-build name — you save them once and they apply org-wide.
| RPC | HTTP | streaming |
|---|---|---|
SaveBuildSecrets | PUT /v1/ignite/builds/secrets | unary |
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 yourDockerfile.git_credentials— a PAT for cloning private git repos; auto-applied togit_sourcebuilds.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 (seeBuild.build_args).
Request
| Field (proto) | HTTP (pbjson) | Type | Notes |
|---|---|---|---|
registry_credentials | registryCredentials | map<string, string> | Registry URL → auth, for pushing images / pulling private base images. |
git_credentials | gitCredentials | GitCredentials | PAT for cloning private git repos. |
build_secrets | buildSecrets | map<string, string> | Extra values exposed as build args; redacted to *** in build records. |
GitCredentials:
| Field (proto) | HTTP (pbjson) | Type | Notes |
|---|---|---|---|
username | username | string | Git username. |
password | password | string | Personal access token (PAT). |
HTTP
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
HTTP
{
"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
- Builds — overview
- Build concepts — sources, caching, image refs
- Builds API —
CreateBuildand the rest - Compute — image-mode runs the built image
- Secrets — the named SecretService slots used by Compute BYOI
- Conventions — transport, auth, wire format, streaming