CFE-4681: document timer_policy attribute on classes: promises (3.27)

content/examples/example-snippets/software_and_patch_installation_1_2_3.cf

@@ -2,7 +2,7 @@
 body common control
 {
   bundlesequence => { "packages" };
-  inputs => { "cfengine_stdlib.cf" }
+  inputs => { "cfengine_stdlib.cf" };
 }
 
 bundle agent packages

content/examples/tutorials/manage-ntp.markdown

@@ -618,6 +618,7 @@ bundle agent ntp
       "servers"
         slist => getvalues("def.ntp[config][servers]"),
         if => isvariable("def.ntp[config][servers]");
+}
 ```
 
 Notice two promises were introduced, one setting `driftfile` to the value of `$(def.ntp[config][driftfile])` if it is defined and one setting servers to the list of values for `def.ntp[config][servers]` if it is defined. [Augments][Augments] allows for variables to be set in the _def_ bundle scope very early before policy is evaluated.

content/reference/components/cf-agent.markdown

@@ -529,7 +529,7 @@ body agent control
   copyfrom_restrict_keys => {
     "SHA=6565a8e647e61e4a7ff2c709e0fe772acce2e45aaa294b2bb713de0ba5a6d8c3",
     "SHA=727dd7f6f8b2344c6d69cf1d3ed0446c0f9f095ce1a114481d691bf1cb2b300d",
-  }
+  };
 }
 ```
 

content/reference/components/cf-execd.markdown

@@ -43,7 +43,7 @@ body executor control
   mailto => "cfengine@example.org";
   mailfrom => "cfengine@$(host).example.org";
   smtpserver => "localhost";
-  schedule => { "Min00", "Min30" }
+  schedule => { "Min00", "Min30" };
 }
 ```
 

content/reference/promise-types/classes.markdown

@@ -301,6 +301,52 @@ classes:
 
 **See also:** [`persistence` classes attribute][classes#persistence], [`persist_time` in classes body][Promise types#persist_time]
 
+### timer_policy
+
+**Description:** Determines whether a persistent class restarts its counter
+when rediscovered.
+
+When a [`persistence`][classes#persistence] timer is set, `timer_policy`
+controls what happens on later runs while the class is still defined (loaded
+from the persistent store):
+
+- `reset` re-evaluates the promise and restarts the timer, so the class keeps
+  persisting for as long as the policy keeps running and the expression stays
+  true.
+- `absolute` preserves the original expiry. While the class is already defined
+  the promise is skipped, so the class disappears once the original timer
+  elapses, regardless of how often the policy runs.
+
+This is the counterpart of `timer_policy` in the classes body, which has always
+defaulted to `reset`.
+
+**Type:** (menu option)
+
+**Allowed input range:** `absolute|reset`
+
+**Default value:** absolute
+
+**Example:**
+
+```cf3
+bundle common setclasses
+{
+  classes:
+    "cached_class"
+      expression => "any",
+      persistence => "120",
+      timer_policy => "reset";
+}
+```
+
+**History:**
+
+- Introduced in CFEngine 3.27.2.
+- The default is `absolute`, preserving the historical persistent-class
+  behavior. The default changed to `reset` in 3.28.0.
+
+**See also:** [`persistence` classes attribute][classes#persistence], [`timer_policy` in classes body][Promise types#timer_policy], [`persist_time` in classes body][Promise types#persist_time]
+
 ### not
 
 **Description:** Evaluate the negation of string expression in normal form

content/reference/promise-types/files/_index.markdown

@@ -2063,7 +2063,7 @@ body file_select example
 {
   leaf_name => { "prog.pid", "prog.log" };
   path_name => { "/etc/.*", "/var/run/.*" };
-  file_result => "leaf_name.path_name"
+  file_result => "leaf_name.path_name";
 }
 ```
 

content/resources/additional-topics/distributed-scheduling.markdown

@@ -184,6 +184,7 @@ bundle agent workflow_one
       "/usr/local/bin/my_job",
         action => if_elapsed("100"),
         classes => state_repaired("did_my_job");
+}
 ```
 
 ## Fancy distributed encapsulation
@@ -366,6 +367,7 @@ bundle agent workflow_one
       "/usr/local/bin/my_job",
         action => if_elapsed("100"),
         classes => state_repaired("did_my_job");
+}
 ```
 
 ## Self-healing workflows

content/resources/additional-topics/security.markdown

@@ -450,6 +450,7 @@ bundle agent change_management
       ),
       depends_on => { "grant_hash_tables" },
       action => neighbourwatch("File changes observed on $(neighbours)");
+}
 ```
 
 It works by building a list of neighbours for each host. The function peers can