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/pdk_testing.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,25 @@ send your validation output to a file in either JUnit or text format.
125
125
command [reference](pdk_reference.md#).
126
126
127
127
128
+
### Ignoring files during module validation
129
+
130
+
There are times when certain files can be ignored when validating the contents of a Puppet module. PDK provides a configuration option to list sets of files to ignore when running any of the validators.
131
+
132
+
To configure PDK to ignore a file, use `pdk set config project.validate.ignore`.
133
+
The `project.validate.ignore` setting accepts multiple files. To add one or more files, run the command for each file or pattern you want to add.
134
+
135
+
For example, to ignore a file called `example.yaml` in the folder called `config`, you would run the following command:
136
+
137
+
```
138
+
pdk set config project.validate.ignore "config/example.yaml"
139
+
```
140
+
141
+
To add a wildcard, use a valid [Git ignore pattern](http://git-scm.com/docs/gitignore):
142
+
143
+
```
144
+
pdk set config project.validate.ignore "config/*.yaml"
145
+
```
146
+
128
147
## Unit testing modules
129
148
130
149
Create and run unit tests to verify that your Puppet code compiles on supported
@@ -211,4 +230,3 @@ correctly performs the functions you expect it to.
211
230
PDK reports what Ruby and Puppet versions it is testing against, and after tests
212
231
are completed, test results. For a complete list of command options and usage
213
232
information, see the PDK command [reference](pdk_reference.md#).
0 commit comments