This documentation supports the 20.08 (12.1) version of BMC Discovery.To view an earlier version of the product, select the version from the Product version menu.

File node

A File node is most often used to track a configuration file. The files that are tracked for each OS are specified by patterns. File nodes are under the full control of patterns.

For detailed information about patterns, see the The-Pattern-Language-TPL and Configipedia.

File node lifecycle

The following section describes the scenarios in which a File node is created, updated or removed.

Creation/update

This is under the full control of patterns and as a result there is no default File node behavior.
 The generated key for a File node is entirely dependent on the pattern that creates the File node.

Removal

A File node can be destroyed in one of following ways:

  • Explicitly by the pattern that created it. See Removal in the Pattern Language guide
  • If the File node is triggered from another Inferred node, then when this inferred node is destroyed, so will the File node. This is a Cascade Removal type, see Cascade Removal.
  • Manually, by selecting the necessary File node, and picking Destroy from the Actions list.

File node attributes

The attributes and relationships on a File node are described in the tables below.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
 

File node relationships

The relationships on a File node are described in the table below.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*