On Mon, Apr 15, 2019 at 2:34 PM Noumbissi Valere <noumbissival...@gmail.com>
wrote:
> 😁 Thanks Fed,
> So if say i have understood the problem, then we are saying, system should
> be able to find the variable in template.config and replace it's value with
> the default value supplied by the designer or the user of the import
> template.
>
The user who imports the template will have to set the variables which will
likely change from network to network.
> say for example, one writes
> {"dns_servers": "4.4.4.4"} in the variable field, then the system should
> find *dns_servers* settings in template.config and replace it's value with
> "4.4.4.4" and this should be done at the level of the template and not
> device configuration.
> If am wrong, please correct me.
>
Not only the system finds the variable, but it should be able to provide a
key/value widget (like the one we use for editing the configuration) that
allows users to change the values of the variable.
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to openwisp+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
