Known Issues
If the site has syndicated content which relies on the config, trying to use config via config split or other means that doesn't have the required config will likely break.
Affected Applications/Limitations
- Acquia Content Hub - 8.x-2.x
Resolution
There are two options to resolve this:
- Update the config split to include the missing config so it matches the new data model needed for the syndicated entities.
- Follow this ticket on drupal.org that introduces code to syndicate only content entities (not config entities) while logging the differences in config. https://www.drupal.org/project/acquia_contenthub/issues/3083430
Note: the second option will still require manually updating the config, for now, as the code still needs to be produced, reviewed and tested.