thentication method to use (e.g. service-account).ZENML_SECRETS_STORE_AUTH_CONFIG: The GCP Service Connector configuration, in JSON format (e.g. {"project_id":"my-project","service_account_json":{ ... }}).

Note: The remaining configuration options are deprecated and may be removed in a future release. Instead, you should set the ZENML_SECRETS_STORE_AUTH_METHOD and ZENML_SECRETS_STORE_AUTH_CONFIG variables to use the GCP Service Connector authentication method.

ZENML_SECRETS_STORE_PROJECT_ID: The GCP project ID to use. This must be set to the project ID where the GCP Secrets Manager service that you want to use is located.

GOOGLE_APPLICATION_CREDENTIALS: The path to the GCP service account credentials file to use for authentication. This must be set to a valid GCP service account credentials file that has access to the GCP Secrets Manager service that you want to use. If you are using a GCP service account attached to a GKE cluster to authenticate, you can omit this variable. NOTE: the path to the credentials file must be mounted into the container.

These configuration options are only relevant if you're using Azure Key Vault as the secrets store backend.

ZENML_SECRETS_STORE_TYPE: Set this to azure in order to set this type of secret store.

ZENML_SECRETS_STORE_KEY_VAULT_NAME: The name of the Azure Key Vault. This must be set to point to the Azure Key Vault instance that you want to use.

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. The following configuration options are supported:

ZENML_SECRETS_STORE_AUTH_METHOD: The Azure Service Connector authentication method to use (e.g. service-account).

ZENML_SECRETS_STORE_AUTH_CONFIG: The Azure Service Connector configuration, in JSON format (e.g. {"tenant_id":"my-tenant-id","client_id":"my-client-id","client_secret": "my-client-secret"}).