Project

General

Profile

« Previous | Next » 

Revision 6bc00e34

Added by Alexis Mousset about 7 years ago

Fixes #10363: Variable * techniques description refers to CFEngine technical vocabulary

View differences:

techniques/fileDistribution/copyGitFile/2.1/metadata.xml
<DESCRIPTION>File comparison method</DESCRIPTION>
<LONGDESCRIPTION>This is the method to use for comparison between source and destination files.
- "mtime" copies the file if the modification time of the source file is more recent than that of the promised file.
- "ctime" CFEngine copies the file if the creation time of the source file is more recent than that of the promised file.
- "atime" CFEngine copies the file if the modification time or creation time of the source file is more recent than that of the promised file. If the times are equal, a byte-for-byte comparison is done on the files to determine if it needs to be copied.
- "ctime" copies the file if the creation time of the source file is more recent than that of the promised file.
- "atime" copies the file if the modification time or creation time of the source file is more recent than that of the promised file. If the times are equal, a byte-for-byte comparison is done on the files to determine if it needs to be copied.
- "exists" copies the file if the promised file does not already exist.
- "binary" copies the file if they are both plain files and a byte-for-byte comparison determines that they are different. If both are not plain files, CFEngine reverts to comparing the mtime and ctime of the files. If the source file is on a different machine (i.e., network copy), then hash is used instead to reduce network bandwidth.
- "binary" copies the file if they are both plain files and a byte-for-byte comparison determines that they are different. If both are not plain files, the agent reverts to comparing the mtime and ctime of the files. If the source file is on a different machine (i.e., network copy), then hash is used instead to reduce network bandwidth.
- "digest" copies the file if they are both plain files and a MD5 message digest comparison indicates that the files are different.
The "digest" option is set by default but may offer poor performance on large numbers (over 100) of file copies - in that case use "mtime" instead.</LONGDESCRIPTION>
<ITEM>
techniques/systemSettings/misc/genericCommandVariableDefinition/3.0/metadata.xml
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
<TECHNIQUE name="Variable from command output (string)">
<DESCRIPTION>Configures a generic CFEngine variable in a common bundle from the output of an executable, to be used in another Technique. This Technique does nothing by itself, you must reuse the variable(s) you will create here in another Technique with the form: $(generic_cmd_var_def.variablename)</DESCRIPTION>
<DESCRIPTION>Defines a variable from the output of a command. Its value can be used in other Directive parameters with the following syntax: ${generic_cmd_var_def.variablename}</DESCRIPTION>
<COMPATIBLE>
<OS>Every OS</OS>
<AGENT version=">= 3.2.4">cfengine-community</AGENT>
......
<DESCRIPTION>Variable name for the output of this command</DESCRIPTION>
<CONSTRAINT>
<TYPE>string</TYPE>
<REGEX error="Please enter a valid CFEngine variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
<REGEX error="Please enter a valid variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
</CONSTRAINT>
</INPUT>
<INPUT>
......
<SECTION name="Advanced settings" displayPriority="low">
<SELECT1>
<NAME>GENERIC_COMMAND_VARIABLE_SHELL</NAME>
<DESCRIPTION>Use system shell or CFEngine system</DESCRIPTION>
<DESCRIPTION>Use system shell</DESCRIPTION>
<LONGDESCRIPTION>
Use of a shell has both resource and security consequences. A shell consumes an extra process and inherits environment variables,
reads commands from files and performs other actions beyond the control of CFEngine.
reads commands from files and performs other actions beyond the control of the agent.
If one does not need shell functionality such as piping through multiple commands then it is best to manage without it.</LONGDESCRIPTION>
<ITEM>
<VALUE>useshell</VALUE>
techniques/systemSettings/misc/genericVariableDefinition/2.0/metadata.xml
-->
<TECHNIQUE name="Variable (string)">
<DESCRIPTION>Configures a generic CFEngine variable in a common bundle, to be used in another Technique. This Technique does nothing by itself, you must reuse the variable(s) you will create here in another Technique with the form: ${generic_variable_definition.variablename}</DESCRIPTION>
<DESCRIPTION>Defines a variable. Its value can be used in other Directive parameters with the following syntax: ${generic_variable_definition.variablename}</DESCRIPTION>
<COMPATIBLE>
<OS>Every OS</OS>
<AGENT version=">= 3.1.5">cfengine-community</AGENT>
......
<DESCRIPTION>Variable name</DESCRIPTION>
<CONSTRAINT>
<TYPE>string</TYPE>
<REGEX error="Please enter a valid CFEngine variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
<REGEX error="Please enter a valid variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
</CONSTRAINT>
</INPUT>
<INPUT>
techniques/systemSettings/misc/variableFromJsonFile/1.0/metadata.xml
-->
<TECHNIQUE name="Variable from JSON file (dict)">
<DESCRIPTION>Downloads a JSON file from shared-files and reads it into CFEngine variables. You can use these variables in the form ${your_namespace.variable_name}</DESCRIPTION>
<DESCRIPTION>Downloads a JSON file from shared-files and reads it into variables. You can use these variables in the form ${your_namespace.variable_name}</DESCRIPTION>
<MULTIINSTANCE>true</MULTIINSTANCE>
<COMPATIBLE>
<OS>Every OS</OS>
......
<DESCRIPTION>Variable namespace, the prefix that will be used for variables definition</DESCRIPTION>
<CONSTRAINT>
<TYPE>string</TYPE>
<REGEX error="Please enter a valid CFEngine variable namespace"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
<REGEX error="Please enter a valid variable namespace"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
</CONSTRAINT>
</INPUT>
<INPUT>
......
<DESCRIPTION>Variable name</DESCRIPTION>
<CONSTRAINT>
<TYPE>string</TYPE>
<REGEX error="Please enter a valid CFEngine variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
<REGEX error="Please enter a valid variable name"><![CDATA[ [a-zA-Z][a-zA-Z0-9_]* ]]></REGEX>
</CONSTRAINT>
</INPUT>
<INPUT>

Also available in: Unified diff