Secrets
Register project-local credential references while keeping secret values out of the RestoreTrust API.
Loading documentation…
A RestoreTrust secret is metadata that points to a secret already present in the worker's Kubernetes environment. The API stores the reference, not the credential value.
Create the Kubernetes Secret in the worker environment first. Send only its
local_secret_name to RestoreTrust.
Use s3, ftp, sftp, or smb for source credentials. Schedules can also reference:
archive_password for a password-protected ZIP backupage_identity for age identity-file decryptionage_passphrase for age passphrase decryptionlocal_secret_name must be a valid lowercase Kubernetes object name and cannot refer to the worker identity secret.
Secret values are never returned. You can update name, description, local_secret_name, or set status to active or paused. The service type is immutable.
A secret cannot be paused or deleted while a source or schedule references it. List filters support name, service_type, and status.
Required scopes are v1.secrets:read, v1.secrets:write, and v1.secrets:delete.