- Status changed to Fixed
8 months ago 9:32am 20 October 2023 Automatically closed - issue fixed for 2 weeks with no activity.
Config ignore only works correctly if it had been configured prior to the config import that is ignoring things.
This is because the setting of what to ignore is taken from the active storage and enhanced by a alter hook.
While it is great that the alter hook is cached, this means that newly deployed config ignore rules only take effect on the second config import.
Add some config to production (say a webform)
Add a rule to ignore the webform in dev
deploy the configuration
Now the webform is deleted because it only exists on production, and the config to ignore it is imported at the same time.
Config Split 2.x has a solution to this problem.
Copy the solution to config ignore
* Study the code of config split
* Port the solution to use the split settings from the transforming storage for config import.
* refactor how the rules are checked.
none
none
none
Fixed
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.