turbo, then map it to a plugin option with the secrets field in your pipeline YAML.
Turbo secrets are for plugin options. Sink credentials (database, Kafka, S3, and others) use the other secret types and the
secret_name field. Turbo secrets do not appear in the sink secrets UI or in the interactive goldsky secret create prompt.Manage secrets
Turbo secrets use the standardgoldsky secret commands. The value is JSON with type set to turbo and value set to the credential.
To create a secret:
CUSTOM_SOURCE_SECRET is an example. Choose any name, and use the same name in the pipeline’s secrets map.
To change the value:
goldsky secret update does not check the existing type. Make sure the name belongs to a turbo secret, and keep "type":"turbo" in the value: if you change the type, pipelines that map the secret fail to deploy.
To list secrets (the Type column shows turbo) and to remove one:
goldsky turbo apply also picks up the new value.
Use a secret in a pipeline
Add asecrets map to a plugin source, transform, or sink, or to a dataset source that expands into one (such as zama.decrypted_transfers). Each key is a plugin option; each value is the name of a secret. A turbo secret passes its value as is. A jdbc secret passes a Postgres connection URL, for plugins that take a database URL.
- A name in
secretsis not a turbo orjdbcsecret. secretsis not a map of option names to secret names.- Two nodes of the same plugin type map the same option to different secrets. The plugin reads one environment variable per option, so a pipeline holds one value per type and option.
Next steps
Zama decrypted transfers
Stream ERC-7984 transfers with amounts decrypted by your delegate key.
CLI reference
All Turbo CLI commands.