If the config footprint of a plugin gets changed, e.g. a new field gets added or the type of an existing one gets changed, then we recommend to run drush eca:update to update all existing models accordingly.
Some maintainers want to automate that with an update hook, but writing that code is cumbersome.
Provide that code from the drush command as a service, let drush call that service instead then. The same service can then be called by update hooks as well.
Active
2.1
Code
Issue #3501663 by jurgenhaas: Provide eca:update functionality as a...
