When doing just a sync all configuration files are imported into the active store.
Since this is not always what you want a flag like --prevent-import would be a nice feature

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

m.j.laarman created an issue. See original summary.

m.j.laarman’s picture

m.j.laarman’s picture

Title: Prevent import when sync » Prevent import when doing config-sync
Status: Needs work » Needs review
scott.whittaker’s picture

This would be extremely useful, I will give this a try soon.

We prefer the ability to manually review configuration changes and pick and choose what to sync, and unfortunately the only way to get new configuration is to do a complete sync.

This can be a problem because we have found that for some edge cases where configuration export is incomplete, it breaks functionality when imported. For example we have some Views with OpenLayers maps configurations that don't export the Openlayers-specific Views settings. When a sync is done, the Openlayers settings are lost and our map views break. We then have to manually edit and fix them all after every sync. But because they are Views, we still do want to keep the Views config tracked so that they can be synced when something important changes.

So there really does need to be a way to have the Configuration Manager pick up new config from the file store and allow config (new and existing) to be selectively imported into the datastore.

The other reason is that configuration sync is an extremely slow process that is prone to timeouts and selective syncing should be a lot more efficient.

scott.whittaker’s picture

Unfortunately this does not import new config and newly tracked items are not added. So there is still no way to track and import new config without also pulling in all existing config. In which case I'm not sure what the point of this patch is? Why would you want to sync without importing? What in this context does that even mean?