dcloud secrets sources createConnect a source — the credential is verified, then stored as a secret
Synopsis
dcloud secrets sources create --name name --provider provider --credential credential [flags]Flags
--nameRequiredstring
The source’s name, 2 to 63 lower-case letters, digits and hyphens, unique in the organization (409 if taken). Its credential is stored as the secret SOURCE_<NAME>_TOKEN, which must not exist yet (409).
Constraints: 2-63 chars, /^[a-z0-9][a-z0-9-]*$/
--descriptionOptionalstring
Free-text description, up to 256 characters
Constraints: max 256 chars
--providerRequiredenum
onepassword (a 1Password service account) or vault (HashiCorp Vault or OpenBao)
One of:
onepassword,vault--credentialRequiredstring
The provider credential, 8 to 8192 characters: a 1Password service-account token (ops_…), a Vault token, or an AppRole secret ID. Verified with the provider before anything is stored (rejected: 422), then encrypted as a secret.
Constraints: 8-8192 chars
--configOptionalmap of string
Provider settings, at most 16 keys, each value up to 512 characters. Vault/OpenBao: address (https, required), namespace, authMethod (token or approle), roleId and approleMount (AppRole). 1Password: none. Omitted: {}. Settings the provider does not accept are 400.
Constraints: key=value
--key-idOptionalstring
The KMS key the credential is encrypted under. Omitted: the organization’s default key, else its first enabled encrypt/decrypt key (none: 409). A key that is unknown, disabled or not encrypt/decrypt is 409.
Constraints: uuid
--refresh-interval-minutesOptionalnumber
Minutes between scheduled syncs, 5 to 1440. Omitted: 60.
Constraints: integer, 5-1440
Example
dcloud secrets sources create --name example --provider onepassword --credential exampleGenerated from the API description, the same one the API checks requests against and the CLI is built from.