| Age | Commit message (Collapse) | Author |
|---|
|
The original messages were added before edit-level was properly
implemented as a field of the session record.
|
|
Return help strings and values in the form used by bash completion.
|
|
Get the potential node type of a path, preliminary to any validation of
values.
|
|
Check whether a given config path has a form compatible with the
reference tree, irrespective of validity of values.
|
|
|
|
|
|
|
|
Occasionally, it is useful to update the config tree _during a commit_
with non-actionable data (meaning data not required for the actions of
currently invoked config_mode scripts): the classic example is that of
removing the entries of plaintext passwords and adding the encrypted
entry. Add the relevent requests and session record field.
|
|
Add optional protobuf fields to convey environment variables USER and
SUDO_USER, as needed for some config_mode scripts. Add non-option fields
to the session record type, defaulting to the empty string.
|
|
The request session_update_pid is not useful, possibly dangerous, in the
current design. Remove and add a simple session_exists for use in client
initialization.
|
|
Enforce consistent naming style according to
https://protobuf.dev/programming-guides/style/
|
|
Merging before passing to the backend results in re-validation of
existing paths in the proposed config; this is unavoidable with the
legacy backend. For vyconf, send the merge proposal with the request, so
validation is only required on new paths.
|
|
|
|
Request cache of session running and proposed configs for loading on
intialization of Config instance. As used elsewhere (for example
vyos-commitd), this is a much faster method of exchanging information
than render and re-parse.
|
|
|
|
|
|
In practice, this may be passed in the request as the ppid, as needed
for CLI applications to coordinate with the ambient config session. For
other uses, the client pid will suffice.
|
|
For auto-generation of Python classes, it is simpler to maintain
syntactical consistency; as these operations will be wrapped in any
client definitions, verbosity is forgivable.
|
|
|
|
|
|
|
|
The message and enum name Status conflicts with the use in vycall.proto;
as the latter has consistency with other (non-conflicting) uses of the
term, rename the former.
|
|
|
|
|
|
|
|
An empty protobuf message does not correctly generate encode/decode
functions. This appears to be fixed upstream, but for now, use
workaround of adding a reasonable field.
|
|
|
|
Regenerate protobuf files:
ocaml-protoc --ml_out src/ data/vyconf.proto
The generated files vyconf.* are renamed vyconf_pbt.* instead of the
split into vyconf_pb/vyconf_types as in the original implementation.
|
