menu:build:templates:tpl_usage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
menu:build:templates:tpl_usage [2021/10/21 09:39] – ↷ Page moved from menu:operate:configs:tpl_usage to menu:build:templates:tpl_usage pgels | menu:build:templates:tpl_usage [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{indexmenu_n> | ||
+ | |||
+ | ===== Template usage ===== | ||
+ | |||
+ | Use the template usage tool to find out which node(s) are using a main-, sub- or port template: you can also filter on the desired client type. | ||
+ | |||
+ | ==== Filter on client type ==== | ||
+ | |||
+ | The " | ||
+ | |||
+ | To limit the number of menu items, the " | ||
+ | |||
+ | Normally the operator will first select the Client-type to narrow the set of main/ | ||
+ | |||
+ | It is possible to apply a Main-template and a Sub-template selection, or a Main-template and a Port-template selection at the same time, but not a Sub-template and Port-template simultaneously. | ||
+ | |||
+ | The resulting set of nodes can be used for reporting purposes, but is more commonly used to create a set of Command-jobs to push an updated Sub-template to the nodes using it. When doing so, please be aware that if the Sub-template is included using a conditional, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ==== Filter on client type and main template ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ==== Filter on client type and sub template ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ==== Filter on client type and port template ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | |||
+ | |||