Azure DevOps Build Definitions

Build definitions render as structured tables for variables, triggers, repositories, schedules, jobs, and outputs.

azuredevops

Terraform often marks build definition nested blocks as sensitive, which makes raw plans nearly impossible to review. tfplan2md turns those blocks into structured tables while preserving secret masking.

Azure DevOps Build Definition Tables
➕ azuredevops_build_definition example2 — 🆔 example-pipeline

Pipeline Name: example-pipeline

Path: \Pipelines

Agent Pool: Azure Pipelines

Variables

Name Value Is Secret Allow Override
🆔 BUILD_CONFIGURATION Release ❌ false ✅ true
🆔 BUILD_PLATFORM Any CPU ❌ false ✅ true

Repository

Type Repo ID Branch YAML Path Report Build Status
TfsGit 🗃️ Infrastructure-Platform (80128bc2-17ff-45f8-ad59-d7609a605c75) ⎇ refs/heads/master azure-pipelines.yml ✅ true 
<details style="margin-bottom:12px; border:1px solid rgb(var(--palette-neutral-10, 153, 153, 153)); padding:12px;">
<summary>➕ azuredevops_build_definition <b><code>example2</code></b> — <code>🆔 example-pipeline</code></summary>
<br>

**Pipeline Name:** <code>example-pipeline</code>

**Path:** <code>\Pipelines</code>

#### Variables

| Name | Value | Is Secret | Allow Override |
| ---- | ----- | --------- | -------------- |
| `🆔 BUILD_CONFIGURATION` | `Release` | `❌ false` | `✅ true` |
| `🆔 BUILD_PLATFORM` | `Any CPU` | `❌ false` | `✅ true` |

#### Repository

| Type | Repo ID | Branch | YAML Path | Report Build Status |
| ---- | ------- | ------ | --------- | ------------------- |
| `TfsGit` | `🗃️ Infrastructure-Platform (80128bc2-17ff-45f8-ad59-d7609a605c75)` | `⎇ refs/heads/master` | `azure-pipelines.yml` | `✅ true` |
</details>

Included Tables

  • Variables, including secret flags and allow-override state
  • CI and pull request trigger settings
  • Repository type, mapped repository name, branch, and YAML path
  • Terraform outputs produced by the Azure DevOps example plan

Learn More

Build definitions work especially well with Azure DevOps principal and repository mapping, so GUID-heavy plans become readable immediately.

Related Documentation