Agent Harness Tutorial · Tech stack
L15 · Release & config
Prompt, model and policy versioned and rolled back together. Family: Change · between releases.
Why our choiceA versioned prompt + model + policy bundle on Azure's config and revisions gives a canary and a rollback without extra tooling.
| Option | Where from | Verdict | Why |
|---|---|---|---|
| App Configuration | ours | ✓ chosen | kill switch, limits, model per job |
| Container Apps revisions | ours | ✓ chosen | |
| GitHub Actions + OIDC | ours | ✓ chosen | Bicep + azd |
| App Configuration | Azure | ✓ used | |
| Container Apps revisions | Azure | ✓ used | |
| Container Registry | Azure | ✗ dropped | GitHub's registry instead |
| OpenFeature + flagd, Unleash | open source | · considered | not picked |
| Terraform, Argo CD | open source | · considered | not picked |
How it works inside the harness: The gate.
Compared: How do config and releases change safely?
| Option | From | Verdict | Job | Azure-native | Portable off Azure | Ops burden | Status |
|---|---|---|---|---|---|---|---|
| Azure App Configuration | Azure | chosen | flags, model per job, thresholds | yes | no | low: managed | built: agent.enabled, limits |
| OpenFeature + flagd | open source | alternative | standard flag API + flag daemon | no | yes | we run flagd | listed open source option |
| Unleash | open source | alternative | feature-flag server and UI | no | yes | we run a server, or SaaS | listed open source option |
| Container Apps revisions | Azure | chosen | canary traffic split, rollback | yes | no | low | final |
| Bicep + azd | Azure | chosen | infrastructure as code | yes | no: Azure only | low | built |
| Terraform | open source | alternative | infrastructure as code | via azurerm provider | yes: many clouds | state file to manage | "Bicep or Terraform" |
| Argo CD | open source | not used | GitOps deploys to Kubernetes | no | yes | needs Kubernetes (AKS) | listed open source option |
DecisionFlags, thresholds and model per job live in App Configuration, releases roll out as Container Apps revisions, and infrastructure is Bicep with azd. Terraform is the swap if the team already uses it or needs more than one cloud.
How it is done: the real code
Cut from the live repositories each time the site is built, so it always matches what runs.
config:
adapter: app-configuration
endpoint: {env: AZURE_APP_CONFIGURATION_ENDPOINT}
label: dev scale: {
minReplicas: 0
maxReplicas: 1
rules: [