Running: drush --simulate @sites update ignores the '--simulate' argument, running a real multi-site update.

If it's not supported should be more safe to abort drush with an error instead of ignoring the flag.

Comments

Kafu’s picture

Kafu commented
Title: '--simulate' ignored with 'update' command » '--simulate' ignored and '--yes' implied with 'update' command

Following discussion in #831272: '@sites' alias doesn't work unless drush can find at least one local site at the drupal root, I've retried with the right syntax:
../../drush/drush --simulate /usr/local/home/daniele/drupal/drupal2/drupal/@sites update.
The result is that '--simulate' is ignored, '--yes' is implied and the sites are really updated without any interaction.

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (duplicate)

updatedb needs --simulate support. already filed.

Kafu’s picture

Kafu commented
Status: Closed (duplicate) » Active

Sorry If I re-activate this issue (the duplication should be issue #436988: Add --simulate support to updatedb command and logging, right?). But here there's also the problem of '--yes' that is automatically implied, that should not have relations to '--simulate', right? If I'm wrong, sorry.

owen barton’s picture

owen barton commented

I don't think we have and option but to force enable --yes, as backend invoke commands won't accept user interaction anyway

greg.1.anderson’s picture

greg.1.anderson commented
Version: All-versions-3.0 » 8.x-6.x-dev
Component: Code » Base system (internal API)
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.