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
feat(gitops): add .vapi-ignore for explicit resource opt-out
Pull previously had only two terminal states for a remote resource
missing locally: "new resource, pull it" or "locally deleted, skip
forever (state-tracked intent)". There was no way to say "I don't want
this resource managed by my repo at all" without either letting it
sit broken locally or relying on the deletion-intent state forever.
Add a `.vapi-ignore` file (per-environment, gitignore-style) that lets
users explicitly opt resources out of pull. Ignored resources are
never written to disk and never tracked in state, distinct from
"locally deleted" which keeps a UUID mapping. Skip messages now
distinguish three reasons:
🚫 = matched .vapi-ignore (not tracked)
✏️ = locally modified (preserved)
🗑️ = locally deleted (intent in state)
Pattern syntax is gitignore-flavored with `*`, `**`, and `?` globs
matching against `<folderPath>/<resourceId>`. See
`resources/<env>/.vapi-ignore.example` for documentation.
Copy file name to clipboardExpand all lines: AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ This project manages **Vapi voice agent configurations** as code. All resources
10
10
11
11
**Template-safe first run:** In a fresh clone, prefer `npm run pull:dev:bootstrap` (or the matching env) to refresh `.vapi-state.<env>.json` and credential mappings without materializing the target org's resources into `resources/<env>/`. `push:<env>` will auto-run the same bootstrap sync when it detects empty or stale state for the resources being applied.
12
12
13
+
**Excluding resources from sync (`.vapi-ignore`):** To prevent specific resources from being pulled at all (e.g. assistants owned by another team or legacy resources you don't want to manage), create `resources/<env>/.vapi-ignore` with gitignore-style patterns. See `resources/<env>/.vapi-ignore.example` for syntax and examples. Ignored resources are silently skipped on every pull and never tracked in state — distinct from "locally deleted" which keeps an entry in state.
14
+
13
15
**Learnings & recipes:** Before configuring resources or debugging issues, read the relevant file in **`docs/learnings/`**. Load only what you need:
0 commit comments