Skip to content

Azure DevOps Provider

The azure_devops bundle targets Azure DevOps Services (dev.azure.com) only.

Authentication

YAML
providers:
  azdo:
    kind: azure_devops
    auth:
      kind: token
      config:
        token: ${AZDO_PAT}
        organization: myorg

Environment variables:

  • AZDO_PAT (primary)
  • AZURE_DEVOPS_EXT_PAT (fallback)
  • AZDO_ORGANIZATION

Targets

Kind Purpose
azdo_variable_group Library secret variables
azdo_pipeline_variable Pipeline definition variables
azdo_environment_variable Environment-scoped secrets
azdo_secure_file Encrypted secure files
azdo_keyvault_variable_group Key Vault–linked variable group name mapping

Generators

Kind Purpose
azdo_pat Mint automation PATs when org policy allows

Retrieve limitations

Azure DevOps does not return secret variable values via REST after write. retrieve() is metadata-only for secret targets.

Variable group REST scope

Library variable group reads stay on the project path _apis/distributedtask/variablegroups (under {organization}/{project}). Creates and updates use that same path at organization scope, with no project segment. Azure DevOps returns HTTP 400 (Project information name is not valid for variable group.) when POST or PUT includes the project in the URL. The project is sent in variableGroupProjectReferences instead. This applies to azdo_variable_group and azdo_keyvault_variable_group.

Failed Azure DevOps calls include the service message field in the error text. The raw response body is not printed.

Target ids

Lockfile and --force-target ids include the object name, for example azdo/azdo_variable_group/production-secrets. A provider/kind prefix is enough when the secret has one target of that kind, and the trailing slash is optional:

Bash
secretzero sync -s database_password --force-target azdo/azdo_variable_group

sync --plan compares the manifest with the lockfile. It does not read the live variable group. secretzero drift and a real sync are the checks against Azure DevOps.

secretzero rotate treats a secret with rotation_period and no lockfile entry as due. A fresh clone does not exit 0 with "No secrets need rotation" for those secrets.

Example

See examples/azure-devops-complete.yml.