Age | Commit message (Collapse) | Author |
|
|
|
that already exists.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vyconf doesn't require oasis.
|
|
|
|
|
|
This is useful in the parser and possibly other code that creates
nodes from scratch.
|
|
It will be used for migrating configs if incompatible syntax change is made.
|
|
Subject to improvement and extension to cover more cases.
|
|
|
|
|
|
|
|
|
|
It's problematic for multiple reasons:
1. It's plaintext and is hard to verify
2. If it's wrong, it may have a very "interesting" effect on the
resulting reference tree, such as lots of misplaced nodes
3. It's hardly ever needed as most nodes only go one or two levels deep
in VyOS, such as "service $something" or "interfaces $something",
and I think it's unlikely that other appliances will differ much.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They are trivial to add with printf when needed anyway, and this function
is useful for generating commands from a tree.
|
|
|
|
shortcut for getting children of a non-root node
|
|
|
|
|
|
Unit tests
|
|
unit tests
|
|
|
|
Bad_interface_definition
to make things simpler for callers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add toml and fileutils to the build dependencies information in the README
|
|
|
|
after the value.
|
|
validators.
What's bad is that right now way too many things are aware of the nature of external validators,
and the validators dir (formerly validators hashtable) is passed around a lot.
We'll need to think it through.
|