COUNT_NAME>@<PROJECT_NAME>.iam.gserviceaccount.comUsing the Azure Key Vault as a secrets store backend

The Azure Secrets Store uses the ZenML Azure Service Connector under the hood to authenticate with the Azure Key Vault API. This means that you can use any of the authentication methods supported by the Azure Service Connector to authenticate with the Azure Key Vault API.

Example configuration for the Azure Key Vault Secrets Store:

zenml:

# ...

# Secrets store settings. This is used to store centralized secrets.

secretsStore:

# Set to false to disable the secrets store.

enabled: true

# The type of the secrets store

type: azure

# Configuration for the Azure Key Vault secrets store

azure:

# The name of the Azure Key Vault. This must be set to point to the Azure

# Key Vault instance that you want to use.

key_vault_name:

# The Azure Service Connector authentication method to use.

authMethod: service-principal

# The Azure Service Connector configuration.

authConfig:

# The Azure application service principal credentials to use to

# authenticate with the Azure Key Vault API.

client_id: <your Azure client ID>

client_secret: <your Azure client secret>

tenant_id: <your Azure tenant ID>

Using the HashiCorp Vault as a secrets store backend

To use the HashiCorp Vault service as a Secrets Store back-end, it must be configured in the Helm values:

zenml:

# ...

# Secrets store settings. This is used to store centralized secrets.

secretsStore:

# Set to false to disable the secrets store.

enabled: true

# The type of the secrets store

type: hashicorp

# Configuration for the HashiCorp Vault secrets store

hashicorp:

# The url of the HashiCorp Vault server to use

vault_addr: https://vault.example.com

# The token used to authenticate with the Vault server

vault_token: <your Vault token>

# The Vault Enterprise namespace. Not required for Vault OSS.

vault_namespace: <your Vault namespace>

Using a custom secrets store backend implementation