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: include and exclude driff patterns
* chore: dep
* fix: truncate chars over gh limit
* docs: update digger reference to include new drift includes
* docs: phrasing
Copy file name to clipboardExpand all lines: docs/ce/drift/backendless-scoping-projects.mdx
+34-5Lines changed: 34 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,16 @@
1
1
---
2
2
title: "Backendless: Scope Drift to Specific Projects"
3
-
description: "Scope backendless drift checks to selected projects using dedicated config files"
3
+
description: "Scope backendless drift checks to selected projects using dedicated config file or patterns"
4
4
---
5
5
6
-
In Backendless mode, scope drift by pointing your scheduled workflow at a dedicated config file.
7
6
8
-
## Approach
7
+
8
+
9
+
In Backendless mode, digger provides two means scoping drift detection.
10
+
11
+
12
+
13
+
## Using dedicated config
9
14
10
15
- Create a dedicated `digger.yml` that lists only the projects or blocks you want scanned.
11
16
- Point your drift workflow to that file using the `digger-filename` input.
@@ -57,7 +62,31 @@ jobs:
57
62
digger-filename: digger-drift-dev.yml
58
63
```
59
64
65
+
## Using drift patterns
66
+
67
+
Add `drift_include_patterns` and `drift_exclude_patterns` under `generate_projects` in your main `digger.yml`:
68
+
69
+
```yaml
70
+
generate_projects:
71
+
blocks:
72
+
- block_name: infra
73
+
root_dir: "infra/"
74
+
workflow: default
75
+
include: "**"
76
+
drift_include_patterns:
77
+
- "infra/prod/**"
78
+
- "infra/staging/**"
79
+
drift_exclude_patterns:
80
+
- "infra/_global/**"
81
+
```
82
+
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
+
60
85
## Notes
61
86
62
-
- There is no per-project drift filter in the action; scoping via a dedicated config file is the recommended approach.
63
-
- You can also mark projects with `drift_detection: false` in your main config to disable drift checks for them.
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.
89
+
90
+
## Related
91
+
92
+
- [Backendless Drift via GitHub Actions](/ce/drift/backendless-github-actions)
Glob patterns matched against each project's `dir`. Only matching projects run drift detection. If empty, all projects are included. See [Backendless: Scope Drift to Specific Projects](/ce/drift/backendless-scoping-projects).
Default AWS role configuration for all generated projects. See [AWS Role Configuration](#aws-role-configuration).
394
390
</ParamField>
@@ -512,7 +508,7 @@ Define custom workflows using the `workflows` map. Each workflow can have its ow
512
508
Configure plan and apply stages.
513
509
514
510
<ParamField path="filter_regex" type="string">
515
-
Regular expression to filter which files trigger this stage.
511
+
Regular expression to mask sensitive values from plan output and PR comments. Matches are replaced with `<REDACTED>`. See [Masking sensitive values](/ce/howto/masking-sensitive-values).
0 commit comments