| Age | Commit message (Collapse) | Author |
|---|
|
functional without additional testing.
|
|
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.
|
|
in the node.def. This change only affects display of nodes when -a option is used.
|
|
Post unionfs directory magic until after all actions have been applied to node tree.
|
|
"ENV_SIBLING_POSITION". This value will either be "FIRST" or "LAST" or undefined.
"FIRST" means that the sibling is the first in the list of a common parent, provided that the sibling resides in the same priority group
"LAST" means that the sibling is the last in the list of a common parent, provided that the sibling resides in the same priority group
|
|
end/begin transactions. now only end/begin are called on active nodes.
|
|
|
|
now stops on failure within priority group (expected behavior).
|
|
|
|
action being applied.
|
|
|
|
not promote to enclosing transaction scope.
|
|
|
|
failures to be lost on repeated commits.
|
|
The new command flag is "-a"
|
|
Add headers with prototypes to remove compiler warnings
Make some obvious tables const to avoid any bugs.
|
|
will need to be added later after some reworking of the old node
execution code.
|
|
general case, just happened to show up on qos-walkthrough (after def files were supported in the new
commit).
|
|
qos-walkthrough regression test. haven't tried it but system probably inherently prevents percents from
being used in embedded multinodes.
|
|
|
|
NOT executed if a multinode does not possess a value. Other source cleanup.
|
|
indirection for actions in commit head.
Bug found when review policy_bgp regression failure.
|
|
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).
|
|
user to support the 'old' cli behavior if desired via the -o flag.
|
|
most of the problems related to nested priorities (but not all). also moved node profiling output from debug file
to stdout
(when enabled by the -c flag).
|
|
added default
priorities in priorities file. also fixed bug where interface changes could sweep in portions
of failed configuration on error. now fixed.
|
|
/tmp/cfg-stdout.log
file. Enable with -s flag on commit to view local session data and associated actions.
|
|
failing. To get
additional details (i.e. location of failure and actions associated with nodes) run with the -e
flag.
|
|
processing.
|
|
commit. New commit may be accessed through
my_commit2 binary.
|
