| Age | Commit message (Collapse) | Author |
|---|
|
CREATE, DELETE, END, BEGIN) within a priority tree.
That means that all work (include the commit-check pass) will be
performed on a priority tree before proceeding to the next priority tree.
If a priority tree generates a failure in the commit-check pass
processing will halt on the priority tree and no further processing will
be performed on the priority tree. The failed priority tree will NOT be
copied to the active working directory.
All nodes in the priority tree will execute SYNTAX and COMMIT actions
except for nodes that have been deleted. Note this iteration is
performed on the working tree, so all commit-check nodes will either be
directly modified or have a node down the hierarchy that had been modified.
The working directory and active directory will not be modified until
after all priority trees have been processed.
|
|
Note that commit check only applies in the following cases:
1) On nodes or ancestors of nodes that have been set or modified
2) Does not applied to deleted nodes
Feature developers should:
1) locate commit checks at a common ancestor if checking across a hierarchy
2) expect that the commit check only enforces created behavior (therefore behaves more like a create check).
An additional flag is provided "-f" to allow for full syntax and commit checks. This allows a complete single pass on all syntax and
commit errors. The default behavior is to stop processing on the first error.
|
|
action being applied.
|
|
|
|
to check whether commit is in a delete or set action. The environmental variable is
"COMMIT_ACTION" the value can either be "SET" or "DELETE". The variable is set for the duration of the call being made to the action in the node.def file.
This should allow some simplication of scripts (i.e. such as setting up static routes).
|
|
commit. New commit may be accessed through
my_commit2 binary.
|
