You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `inlined-imports` | boolean | `false` | Resolve `{{#runtime-import …}}` markers at compile time instead of at pipeline runtime. When `false` (default), prompt-body edits do not require recompilation. |
| `inlined-imports` | boolean | `false` | When `true`, resolves all `{{#runtime-import …}}` markers at compile time; the generated YAML is self-contained but prompt-body edits require recompilation. See [runtime-imports.md](docs/runtime-imports.md). |
Controls when `{{#runtime-import ...}}` markers in the markdown body are resolved. Defaults to `false` — leave it unset for most workflows.
566
+
By default (`inlined-imports: false`), any `{{#runtime-import …}}` markers in the agent body — including the implicit marker that reloads the body itself — are resolved at **pipeline runtime**. This means editing the `.md` agent body does not require recompiling the `.lock.yml` pipeline.
567
+
568
+
Set `inlined-imports: true` only when you need a fully self-contained pipeline YAML (e.g., for auditing or air-gapped deployment):
567
569
568
570
```yaml
569
-
inlined-imports: true # Resolve all runtime-import markers at compile time
571
+
inlined-imports: true
570
572
```
571
573
572
-
| Value | Behavior |
573
-
|-------|----------|
574
-
| `false` (default) | Markers resolved at pipeline runtime — prompt-body edits do **not** require recompiling |
575
-
| `true` | Markers resolved at compile time — the generated `.lock.yml` is fully self-contained, but prompt-body edits require `ado-aw compile` |
576
-
577
-
Only set `inlined-imports: true` if you need the pipeline file to be completely standalone (e.g., for environments where the source `.md` file is not accessible at pipeline runtime). See `docs/runtime-imports.md` for full details.
574
+
**Trade-off**: with `inlined-imports: true`, every change to the agent instructions requires running `ado-aw compile` and committing the updated `.lock.yml`. Omit this field (or set it to `false`) for the typical edit-without-recompile workflow.
-`--all-repos` -- **project-scope mode**: search every ado-aw definition in the ADO project, not just those with a local lock file; mutually exclusive with `--definition-ids`
85
+
-`--source <path>` -- filter to definitions whose `# ado-aw-metadata` marker references this template path (e.g. `agents/security-scan.md`); activates the discovery code path; pairs with `--all-repos` to scope across the whole project
84
86
-`--dry-run` -- print the planned set without calling the ADO API
85
87
86
88
### `secrets list [path]`
@@ -91,6 +93,7 @@ Options:
91
93
92
94
-`--json` -- emit machine-readable JSON
93
95
-`--org`, `--project`, `--pat`, `--definition-ids` -- same as `secrets set`
96
+
-`--all-repos`, `--source` -- same as `secrets set`
94
97
95
98
### `secrets delete <name> [path]`
96
99
@@ -99,8 +102,29 @@ Delete a named variable from every matched definition. No-op when the variable i
99
102
Options:
100
103
101
104
-`--org`, `--project`, `--pat`, `--definition-ids` -- same as `secrets set`
105
+
-`--all-repos`, `--source` -- same as `secrets set`
102
106
-`--dry-run` -- print the planned deletion without calling the ADO API
By default, `secrets` commands match ADO definitions by scanning local lock files. Two opt-in flags activate **Preview-driven discovery** instead — useful when local checkouts of every consumer pipeline aren't available:
111
+
112
+
-**`--all-repos`** — search every ado-aw definition in the ADO project, including consumer pipelines that include ado-aw templates but live in other repos. No local checkout of those repos is required.
113
+
-**`--source <path>`** — restrict results to definitions whose `# ado-aw-metadata` marker references the given template path. Useful for fan-out token rotation: `ado-aw secrets set GITHUB_TOKEN --source agents/security-scan.md` updates every pipeline that includes that template across the entire project.
114
+
115
+
Both flags are mutually exclusive with `--definition-ids`. `enable`, `disable`, and `remove` are **not** affected — they retain their source-scoped safety semantics.
116
+
117
+
```bash
118
+
# Rotate GITHUB_TOKEN on every ado-aw pipeline in the project
119
+
ado-aw secrets set GITHUB_TOKEN --all-repos
120
+
121
+
# Update only pipelines that include a specific template
122
+
ado-aw secrets set GITHUB_TOKEN --all-repos --source agents/security-scan.md
123
+
124
+
# Preview which definitions would be updated
125
+
ado-aw secrets set GITHUB_TOKEN --all-repos --dry-run
126
+
```
127
+
104
128
### `enable [path]`
105
129
106
130
Register an ADO build definition for each compiled pipeline discovered under `path` and ensure it is `enabled`. Matches existing definitions by YAML filename first, then by display name; creates a new definition when no match is found.
@@ -240,9 +264,12 @@ ado-aw compile
240
264
# Verify a generated pipeline
241
265
ado-aw check agent.lock.yml
242
266
243
-
# Set GITHUB_TOKEN on all matched pipelines
267
+
# Set GITHUB_TOKEN on all matched pipelines (local lock files)
244
268
ado-aw secrets set GITHUB_TOKEN
245
269
270
+
# Set GITHUB_TOKEN on every ado-aw pipeline in the project (no local checkout needed)
271
+
ado-aw secrets set GITHUB_TOKEN --all-repos
272
+
246
273
# Register pipelines with ADO and set their token in one step
0 commit comments