The Drupal 8 Configuration Management Initiative (CMI) is a straight up game changer for Drupal development and deployment. As much as we all love doing it live, no longer will this kind of human powered configuration replay in production be necessary. Instead, developers will be able to natively export their configuration to code and deploy that configuration to production using the CMI tools.
This session will feature both a basic overview for how CMI will work in Drupal 8 and an advanced overview of how to use CMI with version control as part of a managed development -> testing -> production workflow. Forget the pain that was drush fe and drush fu-all. Come join David Strauss (one of the technical leads for the CMI in Drupal 8) and Matt Cheney (entertaining populist showman) in embracing modern configuration management in all its glory.
- Log in to post comments
Comments
CMI only possible between cloned instances, not a clean install
I think there is an error in the reply on the question asked in the public at 46:45 regarding importing a configuration on a clean Drupal 8 install. The answer given is "Yes, anything short of that would be a bug". But actually importing/syncing only works between CLONED instances of site, not on a CLEAN install. This is also confirmed in the documentation (https://www.drupal.org/documentation/administer/config) under "Workflow using the Drupal UI".
Drupal 8 won't allow an import because the site uuid's (system.site.yml) won't match.
You're right - at least for now
@askibinski, I believe that is corrrect. I have been experimenting with this recently and I could not achieve an identical working clone when starting from a clean install. The site uuid is important, but even when I manually changed the clean install's uuid to match the master site, importing all configuration failed. I think it fails because dependencies are can not be resolved properly, so the configuration is not imported in the correct order.
That said, if it fails in beta1, that doesn't mean it will never work. IMHO the speakers are completely right calling it a bug. If you cannot deploy a complete site this way, how can you ever be sure that a large upgrade (eg. adding multiple content types, fields and modules) will succeed? I certainly hope it will be possible when 8.0.0 is released. If not, deploying a site will mean moving databases around as if it's 2009 again.