9dae5ef83b
This might be slightly controversial, in that you must specify the state if a file would need to be created to perform the action. We no longer implicitly assume that just specifying content is enough. As it turns out, I believe this is safer and more correct. The code to implement this turns out to be much more logical and simplified, and does this removes an ambiguous corner case from the reversed resource code. Some discussion in: https://github.com/purpleidea/mgmt/issues/540 This patch also does a bit of related cleanup.
23 lines
590 B
Plaintext
23 lines
590 B
Plaintext
import "sys"
|
|
import "world"
|
|
|
|
# here are all the possible options:
|
|
#$opts = struct{strategy => "rr", max => 3, reuse => false, ttl => 10,}
|
|
|
|
# although an empty struct is valid too:
|
|
#$opts = struct{}
|
|
|
|
# we'll just use a smaller subset today:
|
|
$opts = struct{strategy => "rr", max => 2, ttl => 10,}
|
|
|
|
# schedule in a particular namespace with options:
|
|
$set = world.schedule("xsched", $opts)
|
|
|
|
# and if you want, you can omit the options entirely:
|
|
#$set = world.schedule("xsched")
|
|
|
|
file "/tmp/mgmt/scheduled-${sys.hostname()}" {
|
|
state => "exists",
|
|
content => template("set: {{ . }}\n", $set),
|
|
}
|