[pmg-devel] [PATCH pmg-api v2] Use ucf to handle template overrides.

Stoiko Ivanov s.ivanov at proxmox.com
Thu Apr 9 09:00:50 CEST 2020

On Thu, Apr 09, 2020 at 07:18:03AM +0200, Dietmar Maurer wrote:
> > By selectively registering the existing template overrides with ucf, users get
> > asked once upon the next upgrade regarding their changes, and then will
> > always get prompted when the shipped default template changes.
> Again, our main upgrade path is using GUI. I guess 99% of all users use the
> GUI to update. 
> So how does that help? Is it really worth the efforts?

Those users who override templates need to use the CLI in any case (to
create the directory and to copy the modified file) - and those are the
ones that will get asked a debconf question (like they do get asked on some
upgrades when config-files change) - those users who never touch the
templates will not notice any change.

for me getting asked/notified by debonf does seem nicer than having to diff
the templates manually after an upgrade.

additionally it could help those users who followed some tutorial on the
web, and copied all templates over - and are surprised that nothing works
(because the postgres template got adapted over a major upgrade)

It might be debatable whether everyone reads the hints and warnings that
flash during upgrade - but that does not change that we should warn/notify
the users.

if the change seems too invasive/problematic (currently I don't see why) -
we can probably add it as a suggestion to the docs (where the templates are

More information about the pmg-devel mailing list