secret-manager create
Note
This feature is not available in dbvr Community.
Synopsis¶
dbvr secret-manager create [-hV]
[--aws.region=<string> --aws.cloudId=<string>
--aws.configurationId=<string>
--aws.configurationName=<string>
[--aws.description=<string>]
|
--azure.vaultName=<string> [--azure.authType=<string>]
[--azure.cloudId=<string>]
[--azure.clientId=<string>]
[--azure.clientSecret=<string>]
[--azure.tenantId=<string>]
[--azure.clientCertificate=<string>]
--azure.globalConfiguration=<true|false>
[--azure.description=<string>]
--azure.configurationId=<string>
--azure.configurationName=<string>
|
--aws-basic.region=<string> [--aws-basic.authType=<string>]
[--aws-basic.awsAccessKey=<string>]
[--aws-basic.awsSecretKey=<string>]
[--aws-basic.awsSessionToken=<string>]
[--aws-basic.awsAssumeRoleName=<string>]
[--aws-basic.globalConfiguration=<true|false>]
[--aws-basic.description=<string>]
--aws-basic.configurationId=<string>
--aws-basic.configurationName=<string>
|
--cyberark.baseUrl=<string> --cyberark.account=<string>
--cyberark.username=<string> --cyberark.apiKey=<string>
--cyberark.policyBranch=<string>
--cyberark.configurationId=<string>
--cyberark.configurationName=<string>
[--cyberark.trustCertificate=<true|false>]
[--cyberark.globalConfiguration=<true|false>]
[--cyberark.description=<string>]
|
--gcp.project=<string> [--gcp.authType=<string>]
[--gcp.cloudId=<string>]
[--gcp.serviceAccountConfig=<string>]
[--gcp.globalConfiguration=<true|false>]
[--gcp.description=<string>]
--gcp.configurationId=<string>
--gcp.configurationName=<string>
|
--vault.vaultUrl=<string> --vault.authType=<value>
--vault.vaultJwtProviderId=<string>
--vault.token=<string> --vault.username=<string>
--vault.password=<string>
--vault.configurationId=<string>
--vault.configurationName=<string>
[--vault.vaultRoleClaim=<string>]
[--vault.globalConfiguration=<true|false>]
[--vault.description=<string>]]
Tip
You can also use global options with this command.
Description¶
Create a new secret manager configuration.
Use one of the provider-specific option groups - --aws.*, --azure.*, --aws-basic.*, --cyberark.*, --gcp.*, or
--vault.* - to define the connection. All required options for the chosen provider must be specified.
Note
--aws.* configures AWS Integrated Cloud Secrets (using an existing AWS Cloud profile), while
--aws-basic.* configures AWS Secrets with region and static credentials.
AWS Integrated Cloud Secrets options¶
--aws.region¶
AWS region where the secrets are stored.
--aws.cloudId¶
AWS Cloud configuration ID used for authentication. Specifies which AWS Cloud profile to use to access the secrets.
--aws.configurationId¶
Unique identifier for this configuration.
--aws.configurationName¶
Display name for this configuration.
--aws.description¶
Optional description.
Azure Key Vault options¶
--azure.vaultName¶
Name of the Azure Key Vault that stores the secrets.
--azure.authType¶
Authentication type. Accepted values: Default credentials, Client certificate, Enterprise application, Client secret,
Cloud Integration.
--azure.cloudId¶
Azure Cloud configuration ID used for authentication. Used when --azure.authType="Cloud Integration".
--azure.clientId¶
Microsoft Entra ID application ID. Used with Client certificate, Enterprise application, and Client secret
authentication.
--azure.clientSecret¶
Secret for the Microsoft Entra ID application. Used when --azure.authType="Client secret".
--azure.tenantId¶
Microsoft Entra ID tenant ID. Used with Client certificate, Enterprise application, and Client secret
authentication.
--azure.clientCertificate¶
Path to the client certificate in PEM or PFX format. Files with the .pfx extension are treated as PFX; other files are
treated as PEM. Used when --azure.authType="Client certificate".
--azure.configurationId¶
Unique identifier for this configuration.
--azure.configurationName¶
Display name for this configuration.
--azure.globalConfiguration¶
Apply this configuration globally across all clients.
--azure.description¶
Optional description.
AWS Secrets options¶
--aws-basic.region¶
AWS region where the secrets are stored.
--aws-basic.authType¶
Authentication type. Accepted values: Access/secret keys, Default credentials.
--aws-basic.awsAccessKey¶
AWS access key. Used when --aws-basic.authType=Access/secret keys.
--aws-basic.awsSecretKey¶
AWS secret key. Used when --aws-basic.authType=Access/secret keys.
--aws-basic.awsSessionToken¶
AWS session token. Used when --aws-basic.authType=Access/secret keys.
--aws-basic.awsAssumeRoleName¶
IAM role to assume when accessing the secrets.
--aws-basic.configurationId¶
Unique identifier for this configuration.
--aws-basic.configurationName¶
Display name for this configuration.
--aws-basic.globalConfiguration¶
Apply this configuration globally across all clients.
--aws-basic.description¶
Optional description.
CyberArk options¶
--cyberark.baseUrl¶
URL of the Conjur OSS server (for example, https://conjur.example.com).
--cyberark.account¶
Conjur tenant or organization account name (for example, myorg).
--cyberark.username¶
Conjur user ID used for authentication.
--cyberark.apiKey¶
API key associated with the Conjur user for authn login.
--cyberark.policyBranch¶
Path to the policy namespace where secrets are stored (for example, dev/app).
--cyberark.configurationId¶
Unique identifier for this configuration.
--cyberark.configurationName¶
Display name for this configuration.
--cyberark.trustCertificate¶
Trust the CyberArk server's SSL certificate without manual import. Enable this if you're using a self-signed certificate or connecting to a server whose certificate isn't trusted by default.
--cyberark.globalConfiguration¶
Apply this configuration globally across all clients.
--cyberark.description¶
Optional description.
Google Cloud Secret Manager options¶
--gcp.project¶
Google Cloud project ID where the secrets are stored.
--gcp.authType¶
Authentication type. Accepted values: Default credentials, Key file, Web Browser, OAuth (Pregenerated),
Cloud Integration.
--gcp.cloudId¶
GCP Cloud configuration ID used for authentication. Specifies which GCP Cloud profile to use to access the secrets.
Used when --gcp.authType=Cloud Integration.
--gcp.serviceAccountConfig¶
Path to the service account key file. Used when --gcp.authType=Key file.
--gcp.configurationId¶
Unique identifier for this configuration.
--gcp.configurationName¶
Display name for this configuration.
--gcp.globalConfiguration¶
Apply this configuration globally across all clients.
--gcp.description¶
Optional description.
Vault options¶
--vault.vaultUrl¶
URL of the Vault server used to retrieve secrets.
--vault.authType¶
Authentication type. Accepted values: OAUTH2, TOKEN, USERNAME_PASSWORD.
--vault.vaultJwtProviderId¶
Path where the JWT authentication method is enabled in Vault (for example, auth/jwt/). Used when
--vault.authType=OAUTH2.
--vault.token¶
Authentication token required to access the Vault server. Used when --vault.authType=TOKEN.
--vault.username¶
Username for Vault authentication. Used when --vault.authType=USERNAME_PASSWORD.
--vault.password¶
Password for Vault authentication. Used when --vault.authType=USERNAME_PASSWORD.
--vault.configurationId¶
Unique identifier for this configuration.
--vault.configurationName¶
Display name for this configuration.
--vault.vaultRoleClaim¶
The claim in the JWT token that contains the Vault role name. If not set, the default role from the Vault provider is used.
--vault.globalConfiguration¶
Apply this configuration globally across all clients.
--vault.description¶
Optional description.
Examples¶
Create an AWS Secrets Manager configuration:
dbvr secret-manager create \
--aws.region=us-east-1 \
--aws.cloudId=my-cloud-profile \
--aws.configurationId=aws-prod \
--aws.configurationName="AWS Production" \
--aws.description="Production secrets"
Create an Azure Key Vault configuration using default credentials:
dbvr secret-manager create \
--azure.vaultName=production-vault \
--azure.authType="Default credentials" \
--azure.globalConfiguration=false \
--azure.configurationId=azure-prod \
--azure.configurationName="Azure Production"
Create a CyberArk configuration:
dbvr secret-manager create \
--cyberark.baseUrl=https://cyberark.example.com \
--cyberark.account=myaccount \
--cyberark.username=admin \
--cyberark.apiKey=myapikey \
--cyberark.policyBranch=Root \
--cyberark.configurationId=cyberark-prod \
--cyberark.configurationName="CyberArk Production"
Create a Google Cloud Secret Manager configuration using a service account key file:
dbvr secret-manager create \
--gcp.project=my-gcp-project \
--gcp.authType="Key file" \
--gcp.serviceAccountConfig=/path/to/service-account.json \
--gcp.configurationId=gcp-prod \
--gcp.configurationName="Google Production"
Create a Vault configuration using token authentication:
dbvr secret-manager create \
--vault.vaultUrl=https://vault.example.com \
--vault.authType=TOKEN \
--vault.token=s.mytoken \
--vault.vaultJwtProviderId=my-jwt-provider \
--vault.username=vaultuser \
--vault.password=vaultpass \
--vault.configurationId=vault-prod \
--vault.configurationName="Vault Production"
Info
For a complete walkthrough - including creating a Vault secret and using it with a datasource - see Secret provider setup example.