nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Execution of iwreset on templating and workflows

stya

Hi,

Am a bit confused here,

iwreset -a needs to be executed if there is a change in TS conf files.

Does it applies to templating(templating.cfg) and workflows(available_templates.cfg) changes as well.Do we need to use iwreset -a if there are changes in above cfg files.

Thanks,
stya

Find more posts tagged with

Comments

Adam Stoller

Hi,

Am a bit confused here,

iwreset -a needs to be executed if there is a change in TS conf files.

Does it applies to templating(templating.cfg) and workflows(available_templates.cfg) changes as well.Do we need to use iwreset -a if there are changes in above cfg files.

Thanks,
stya

Some configuration changes require iwreset, some require iwreset -ui (or a subset thereof) and some require iwreset -a. Unfortunately, most of this is known from experience and some documentation - for example:

That being said - templating.cfg, available_templates.cfg, and available_models.xml are all read in real-time, so you don't need to run iwreset at all for changes to those files.