Repository navigation
URL datastores support #30
Description
Activity
Tom, are we able to get this URL datastores? If possible, how? Is it only questing about writing some other choices into selectbox or do we need some backend logic?
Backend expects parameters according to https://github.com/CESNET/mod_netconf/blob/master/src/README
That means for we need json with these fields and values for URL as a source:
{ type: 9, key: , source: "url", target: "candidate", uri-source: "ftp://myftp.mydomain/my-config.xml"}For URL as a target, use "url" in "target" and "uri-target".
Similar usage is for edit-config that is also described in mod_netconf README.
Currently NetopeerGUI works only with running, startup and candidate datastores. It will be useful to have support for URL datastores.
For example, two or more device operators wants to prepare configuration for some common use cases. First can use candidate datastore and work without problems but the others can not use NetopeerGUI for that purpose. If there would be support for URL datastores, every operator would get his copy of running configuration to separate file on ftp server then switch to this URL datastore, perform changes and eventually copy resulting configuration to running or startup datastore.