David Erni: Package spotlight: ftw.upgrade.
Talk by David Erni at the Plone Conference 2019 in Ferrara.
The upgrade-step:directory ZCML directive allows us to use a new upgrade step definition syntax. Less room for typos. Upgrades in the given directory are auto-discovered. Each directory is a generic setup upgrade profile. You no longer need a profile version in metadata.xml.
With the bin/upgrade command you can upgrade your Plone site, install an add-on, upgrade an add-on. This includes progress logging, so you see that something happens during long upgrade steps.
Why do we write upgrades? We want to consistently alter content and configuration. Prevent undocumented changes through the Plone UI: your policy package should have the needed configuration, without relying on manual changes done on the live site. We want to apply a minimal set of changes, instead of reinstalling an add-on.
We have several helpers methods, for example for:
- class migration and in-place migration
- rebuild, add, remove indexes
- update object or workflow security
And there is much more, like deferrable upgrade steps, possible because we separately track which upgrade steps have been executed.
We are working on getting it running on Plone 5.2.