From 8343f2b12a41305c8b62e78a47d27af0381c3848 Mon Sep 17 00:00:00 2001
From: Matthew Grasmick <matt.grasmick@gmail.com>
Date: Mon, 3 Apr 2017 13:36:48 -0400
Subject: [PATCH] Fixes #1014: Don't run drush entity-updates during
 config-import.

---
 phing/tasks/setup.xml | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/phing/tasks/setup.xml b/phing/tasks/setup.xml
index de0960384..8b5218c1b 100644
--- 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