On Thu, Oct 24, 2019 at 4:42 PM Oliver Kraitschy <[email protected]> wrote:
> Am 18.10.19 um 18:30 schrieb Federico Capoano: > > > Nevertheless I'd like to have some more control over the update > process: > > > > - defining the order in which those templates are applied (for > > example to first upload a file to the device and then use it in the > > configuration) > > > > By dragging templates up or down you can define the order in which they > > are merged to generate the final configuration. > > > > Do you mean the order to apply it on the device? > > Am I correct that this does basically define the priority of the templates? > Yes, I rather mean the order in which to apply the templates on the > device. For example, if one template contains a requirement for another > template, then the order would make sure that the first template is > applied before the second template gets rolled out. > I'm not sure I understand the use case scenario well. At the moment the configuration is downloaded, unpacked and installed on the device, only once that is done the services are reloaded, which means that the order in which files are written does not matter much, because services are reloaded only once every file is its place. Why should it matter? Federico -- 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 [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAERYH6URVS%3DoRTHcobzQ%2B%3DSn0heUyeFZTCD-D51kfEOcd6upNw%40mail.gmail.com.
