Skip to content

Added description of when files promisers are interpreted as regular expressions #3745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nickanderson wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added description of when files promisers are interpreted as regular expressions #3745

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions content/reference/promise-types/files/_index.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,16 @@ regular expression that matches any single-character filename, use
Depth search refers to a search for file objects that starts from the
one or more matched base-paths as shown in the example above.

### When is a promiser treated as a regular expression?

CFEngine treats a files promiser as a regular expression if:

- `pathtype => "regex"` is explicitly set.
- `pathtype => "guess"` (the default) is set **and** the promiser contains any of the following:
- `*` or `+` (unescaped)
- `[...]` (character classes)
- `|` inside parentheses `(...)`

### Filenames and regular expressions

CFEngine allows regular expressions within filenames, but only after
Expand Down
Loading