Support option of reverting to config as provided when (re)applying a recipe

Created on 2 September 2022, over 2 years ago
Updated 21 May 2024, 7 months ago

Problem/Motivation

When reapplying a recipe, the most desirable result will likely be #3307646: Merge in config updates when (re)applying a recipe . However, there will still be a use case for reverting config. Per @alexpott in #3283900-6: Define recipe runtime configuration update requirements :

I think we should consider in future allowing recipes to be force applied and overwrite configuration in a more destructive manner - and present diffs etc so people will know what's going to change but I view this as stuff for later. I think for now what we have to do is the straghtforward case of not breaking your site and erroring when the requirements are not met. We can deal with the more complex situations later as the requirements for doing that become more apparent.

Proposed resolution

When reverting is chosen, merge the config as currently provided into a snapshot of the config as previously installed per #2960870: Snapshot configuration as installed and updated from recipes and extensions , so that changes made through config actions are not lost. Then overwrite the active version.

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

11.0

Component

Code

Created by

🇨🇦Canada nedjo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024