vyatta-cfg.git/src/common, branch debian/0.15.23Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git)
https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=debian%2F0.15.232009-10-10T02:44:23+00:00commit post-processing performance optimization2009-10-10T02:44:23+00:00An-Cheng Huangancheng@vyatta.com2009-10-10T02:44:23+00:00urn:sha1:9e85f9cee6d0d923d4d76d5f936bbcb7a0610f26
* convert subshell invocations to library function calls.
* reduce boot time by ~40 seconds for "certain configuration".
escape value slash in leaf value--followon fix to suppression of leaf value with slash in2009-10-05T20:59:14+00:00Michael Larsonmike@ft1.vyatta.com2009-10-05T20:59:14+00:00urn:sha1:6fb487a39a7fab3d568122caf4b1c1d9a17adad8
jenner.
fix for bug 4969. on leaf nodes scan for '/' and don't make these values available to the partial commit status api (bug fix 4919). this approach will2009-10-02T17:47:48+00:00Michael Larsonmike@ft1.vyatta.com2009-09-30T16:36:22+00:00urn:sha1:26cdcb063b6f9422b7ffa4a187a762920e6a651d
be revised in next
release.
add support for value tags on term multinodes. used in debugging output and accounting file.2009-09-11T22:11:56+00:00Michael Larsonmike@ft1.vyatta.com2009-09-11T22:11:56+00:00urn:sha1:bc19150dee5789ca4500439594147caff85e5ddd add leaf values to path data structures. will show in disgnostic output from commit and via .changes2009-09-10T20:42:58+00:00Michael Larsonmike@ft1.vyatta.com2009-09-10T20:42:58+00:00urn:sha1:2cdab905bb8b92a00c8e57e638a9ccbc3244df65
file used for commit active node set.
added data path to environment during commit. value key is "NODE_DATA_PATH". nodes are delimited by "/" rather than spaces.2009-09-05T04:17:23+00:00sliochslioch@eng-140.vyatta.com2009-09-05T04:17:23+00:00urn:sha1:f50e8a9c76156a003d07fbca48f35abd24a434d0fix for bug 4669. Revert string back to value for terminating multinodes.2009-07-06T20:38:22+00:00sliochslioch@eng-140.vyatta.com2009-06-30T20:52:01+00:00urn:sha1:492372480adb0b24808c893b090d12f5703fa3fbupdated perl api for new cli to support working node representation. not yet functional without additional testing.2009-07-06T20:37:44+00:00sliochslioch@eng-140.vyatta.com2009-06-27T06:18:33+00:00urn:sha1:c3b23a060d2c949580873dc100469be9ad05734cThe SYNTAX and COMMIT tags will be executed before an actions (UPDATE,2009-06-26T22:08:02+00:00sliochslioch@eng-140.vyatta.com2009-06-26T22:05:48+00:00urn:sha1:aa697721489c867de9b39121836c05a5bc3239b6
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.
Commit check now behaves like IslaVista.2009-06-24T18:51:45+00:00sliochslioch@eng-140.vyatta.com2009-06-24T18:43:11+00:00urn:sha1:bbf867acfcaa999dec75b3a76ca6d286db4b57f8
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.