🚀 New! Kestra raises $3 million to grow Learn more

This integration will store secrets in Azure Key Vault. Kestra authentications must have "Get", "List", "Set", "Delete", "Recover", "Backup", "Restore", "Purge" permissions.

Authentication

You can authenticate the Secrets Manager with Azure Cloud in multiple ways:

  • Using a user or a service principal secret by setting properties clientId and clientSecret.
  • If none is set, the default authentication will be used e.g. in a similar way as Azure CLI does it.
yaml
kestra:
  secret:
    azure-key-vault:
      clientSecret:
        tenantId: "id"
        clientId: "id"
        clientSecret: "secret"

Others configurations

kestra.secret.azure-key-vault.vaultName

Name of the Azure Key Vault to use.

kestra.secret.azure-key-vault.keyVaultUri

Optionally you can provide the full Azure Key Vault url instead of its name.

kestra.secret.azure-key-vault.prefix

Optional. All key handled by kestra will be prefixed with this. Can be useful to share the same secret manager between Kestra instances.