When a change is made to a schema.yml and/or settings.yml file, for the change to take effect currently you have to uninstall and re-install the module. This is tedious as it loses all Scheduler settings and data. This issue has been cerated to discuss how we can help our users to do this more smoothly, or better still to automate it via a hook_update() function to avoid any manual work.

This issue is a spin-off from quesion (c) that I asked in #2682579-10: Move constants out of global space into settings and schema

Comments

jonathan1055 created an issue. See original summary.

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented
Issue summary: View changes
Related issues: +#2682579: Move constants out of global space into settings and schema

Possibly one way might be to use the Configuration Inspector module as that looks like you may be able to import a .yml file. But there should be an equivalent of 'empty cache' for config so that value are refreshed from the external files immediately. It is only my lack of Drupal knowledge about how and where to find this function - it must exist.

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented

Another useful module is Configuration Update Manager which provides comparisons of the loaded configuration versus the current config files. You can easily reload from file, effectively providing a 'revert' function for all types of configuration. This is especially useful in Views where the 'Revert' operation in 7.x has been dropped in 8.x.

bardiuk’s picture

bardiuk CreditAttribution: bardiuk commented

Is there any progress with this in 2022? I was googling 'how to update schema/settings without un-install/install a module.

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented

Hi ollie-db,
The best way I have found is the config_update module I mentioned in #3. It gives you a visual comparison of the source .yml file compared to the loaded configuration in your site, and you can 'revert to source' which effectively means "reload my sites confiuration to match the modules sourec .yml definition" I have found this very useful.

Do you have a specific schema problem with Scheduler? or was this just an issue you found and your problem is with another module?