Fixes acquia#1014: Don't run drush entity-updates during config-import.

grasmash · Apr 3, 2017 · 8343f2b · 8343f2b
1 parent 6353dcc
commit 8343f2b
Showing 1 changed file with 1 addition and 3 deletions.
diff --git a/phing/tasks/setup.xml b/phing/tasks/setup.xml
@@ -208,9 +208,7 @@
         <!-- This must happen before features are imported or configuration is imported. -->
         <!-- For instance, if you add a dependency on a new extension to an existing configuration file, you must enable that extension via an update hook before attempting to import the configuration. -->
         <!-- If a db update relies on updated configuration, you should import the necessary configuration file(s) as part of the db update. -->
-        <drush command="updb" assume="yes" alias="${drush.alias}" passthru="false">
-          <option name="entity-updates"></option>
-        </drush>
+        <drush command="updb" assume="yes" alias="${drush.alias}" passthru="false"/>
 
         <!-- This will call one of the following:
           setup:config-import:features