You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Template and keystore re-caching would be a welcome feature; more of a nice-to-have. This would allow templates or keystores (or both) to be re-cached without performing a ztp service restart which would interrupt any ongoing downloads.
More useful for keystores, so switch serial numbers can be added to CSVs as they're taken from inventory/unboxed/etc.
Not as necessary for templates, as any changes should be ironed out with test runs before provisioning begins; but sometimes people are tired, haha.
e.g. ztp cache (template <template> | templates) #Recache a single template, or all templates. ztp cache (keystore <keystore> | keystores) #Recache a single keystore, or all keystores
... ztp cache files #Recache all templates and keystores.
The text was updated successfully, but these errors were encountered:
Template and keystore re-caching would be a welcome feature; more of a nice-to-have. This would allow templates or keystores (or both) to be re-cached without performing a
ztp service restart
which would interrupt any ongoing downloads.More useful for keystores, so switch serial numbers can be added to CSVs as they're taken from inventory/unboxed/etc.
Not as necessary for templates, as any changes should be ironed out with test runs before provisioning begins; but sometimes people are tired, haha.
e.g.
ztp cache (template <template> | templates)
#Recache a single template, or all templates.ztp cache (keystore <keystore> | keystores)
#Recache a single keystore, or all keystores...
ztp cache files
#Recache all templates and keystores.The text was updated successfully, but these errors were encountered: