Feature #11
Add more abstract testing mechanism
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Luke Kanies | % Done: | 0% | |
| Category: | language | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
Description
We currently support Facts and ‘==’ for testing. This isn’t going to be nearly enough. Some examples of what Cfengine supports are:
True if file 2 was modified more recently than file 1 (UNIX mtime)
True if file 1 was accessed more recently than file 2 (UNIX atime)
True if file 1's attributes were changed in any way more recently than file 2's (UNIX ctime)
True if the named file object exists.
IPRange(address-range)
True if the current host lies within the specified IP range
True if the current relative domain name begins with basename and ends with an integer between start and stop
True if the named variable is defined. Note well: use the variable name, not its contents (that is, [[IsDefined]](var), and not [[IsDefined]](${var}))
History
#1
Updated by Luke Kanies over 6 years ago
- Status changed from 1 to Closed
- 7 set to wontfix
I don’t think most of these are ever going to happen, and this ticket is too vague to really be looked at anyway.