Console terminology: In the Maverics Console, Orchestrator instances and
configuration delivery are managed through Deployments. When working directly
with YAML, configuration is managed as files delivered via the
-config flag or
MAVERICS_CONFIG environment variable.How Secret Providers Work
Secret providers are configured via theMAVERICS_SECRET_PROVIDER environment variable or the -secretProvider CLI flag — not in YAML configuration. Only one secret provider may be active at a time.
<maverics.client_secret> by fetching it from the configured secret provider. The namespace (maverics) and key (client_secret) map to the secret path and key in the provider.
Available Providers
| Provider | URL Scheme | Use Case |
|---|---|---|
| HashiCorp Vault | hashivault:// or hashivaults:// | Enterprise secret management with dynamic secrets |
| AWS Secrets Manager | awssecretsmanager:// | AWS-native secret storage |
| Azure Key Vault | azurekeyvault:// | Azure-native secret and certificate management |
| Delinea Secret Server | delinea:// | Enterprise privileged access management |
| CyberArk Conjur | conjur:// | DevOps-oriented secrets for CI/CD and containers |
| CyberArk CCP | cyberarkccp:// | CyberArk Central Credential Provider |
| Secret File | secretfile:// | Local file-based secrets for development |
Provider Pages
HashiCorp Vault
Enterprise secret management with dynamic secrets
AWS Secrets Manager
AWS-native secret storage
Azure Key Vault
Azure-native secret and certificate management
Delinea Secret Server
Enterprise privileged access management
CyberArk Conjur
DevOps-oriented secrets for CI/CD and containers
CyberArk CCP
CyberArk Central Credential Provider
Secret File
Local file-based secrets for development