Changes between Version 52 and Version 53 of AppPlanSpec

Timestamp:

Jun 2, 2021, 5:02:51 PM (3 years ago)

Author:

DavidA

Comment:

--

AppPlanSpec

@@ -36 +36 @@
    Use this to favor one class over another.
    For example, if you have both SSE and non-SSE versions, use 1.1 and 1.0 respectively.
- <os_regex>regex</os_regex>:: send only to hosts whose operating system version matches the given regular expression
+ <os_regex>regex</os_regex>:: send only to hosts whose operating system version matches the given regular expression.
+  If the regular expression starts with '!', negate its sense (this is not standard regex notation).
  <min_os_version>x</min_os_version>:: send only to hosts with at least this numerical OS version.
    Numerical OS version derived from the host's os_version string as follows:.
@@ -47 +48 @@
  <cpu_feature>x</cpu_feature>:: a required CPU feature (such as sse3). You can include more than one.
  <host_summary_regex>regex</host_summary_regex>:: send only to hosts with host.serialnum field that matches the given regular expression.
+  If the regular expression starts with '!', negate its sense.
  <cpu_vendor_regex>regex</cpu_vendor_regex>:: send only to hosts whose CPU vendor matches the regular expression.
+  If the regular expression starts with '!', negate its sense.
   Example CPU vendors are "!GenuineIntel" and "AuthenticAMD",
   so to match Intel CPUs you could use
@@ -54 +57 @@
 }}}
  <cpu_model_regex>regex</cpu_model_regex>:: the host's CPU model must match the regular expression.
+  If the regular expression starts with '!', negate its sense.
  <infeasible_random>X</infeasible_random>:: the app version won't be used with probability X.
 
 The following elements let you use a project preference to decide whether to use the app version:
  <project_prefs_tag>x</project_prefs_tag>:: the name of the tag
- <project_prefs_regex>x</project_prefs_regex>:: the contents must match this regular expression
+ <project_prefs_regex>x</project_prefs_regex>:: the contents must match this regular expression.
+  If the regular expression starts with '!', negate its sense.
  <project_prefs_default_true/>:: treat the absence of the project_prefs_tag (i.e. the user didn't set it yet) as if the project_prefs_regex matched.