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
Copy file name to clipboardExpand all lines: docs/ce/drift/backendless-scoping-projects.mdx
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,10 +82,33 @@ generate_projects:
82
82
83
83
Only projects whose `dir` matches an include pattern and does not match an exclude pattern will run drift detection. Exclude patterns are evaluated after include patterns.
84
84
85
+
## Using per-block drift patterns
86
+
87
+
You can also place `drift_include_patterns` and `drift_exclude_patterns` **inside a block**. They apply only to projects generated by that block and are matched against each project's `dir`.
Here, every project generated from the `crdb` block whose directory matches `projects/CRDB/aws/dev/staging/us-east-1/ec2/**` is skipped during drift detection, while everything else in the block runs as usual. The `dev` block is unaffected.
103
+
104
+
Per-block patterns and top-level patterns compose: a project must pass both checks to run drift detection.
105
+
85
106
## Notes
86
107
87
-
- Patterns use [doublestar](https://github.com/bmatcuk/doublestar) glob matching against the project directory path.
88
-
- Both fields default to `[]`. If `drift_include_patterns` is empty, all projects are included.
108
+
- `drift_include_patterns`/ `drift_exclude_patterns` use [doublestar](https://github.com/bmatcuk/doublestar) glob matching against the project directory path.
109
+
- Per-block patterns apply only to projects generated by that block. Explicit `projects:` entries and projects from other blocks are unaffected.
110
+
- Top-level patterns under `generate_projects` apply to every generated project. When both are set, a project must satisfy each independently.
111
+
- All fields default to `[]`. If the include list is empty, every project passes the include step.
Glob patterns matched against the `dir` of each project generated by this block. Only matching projects run drift detection. If empty, every project the block generates passes the include step. Evaluated alongside the top-level `drift_include_patterns` — a project must pass both. See [Backendless: Scope Drift to Specific Projects](/ce/drift/backendless-scoping-projects).
Glob patterns matched against the `dir` of each project generated by this block. Matching projects are skipped during drift detection. Evaluated after this block's `drift_include_patterns`.
0 commit comments