Use higher hardcoded threshold to avoid breaking tasks due to high load on multi-CPU systems when provision can't determine the real load reliably.

anarcat authored May 31, 2013 and Grazyna Jaworska committed Jun 20, 2013

we are not getting all possible contexts because there's no easy way
to enumerate them, so instead we just don't check

Steven Jones authored Sep 11, 2012 and Grazyna Jaworska committed Sep 15, 2012

Issue #1513678 by Jon Pugh, fastangel, Steven Jones: Fixed Hooks based on TASK_NAME should handle task names with dashes in them.

Steven Jones authored Aug 24, 2012 and Grazyna Jaworska committed Aug 26, 2012

Issue #1750974 by Steven Jones: Fixed Unable to pass working-copy or backend-only to hostmaster install.

mig5 authored Aug 17, 2012 and Grazyna Jaworska committed Aug 18, 2012

Issue #1440646 by tstoeckler, cafuego, mig5: Make Drush be runnable as Root with Provision installed.

fix the help information for most provision-commands by removing the site name argument and switch to @aliases instead. add examples for most commands too.

fix the help information for most provision-commands by removing the site name argument and switch to @aliases instead. add examples for most commands too.

This reverts commit 6537cb81.

This reverts commit f7a07113.

The problem with this approach is that if we have sites in the platform
and fail to verify it, removing the apache config would actually break
the platform even more. We do not want that.

What we want is a provision-install on platforms that can be rolled back
properly too. It's harder than this.

when drush make fails, the apache config is already created and wasn't
cleaned up

we hook into the rollback by adding a new magic hook through
command_invoke() that will cascade through the current context and call
the right rollback hook.

we implement one for the platform, but we probably need to implement one
for servers and sites too.

This reverts commit f7a07113.

The problem with this approach is that if we have sites in the platform
and fail to verify it, removing the apache config would actually break
the platform even more. We do not want that.

What we want is a provision-install on platforms that can be rolled back
properly too. It's harder than this.

when drush make fails, the apache config is already created and wasn't
cleaned up

we hook into the rollback by adding a new magic hook through
command_invoke() that will cascade through the current context and call
the right rollback hook.

we implement one for the platform, but we probably need to implement one
for servers and sites too.

this respects the existing convention that hostmaster commands are part of provision, while hosting are in hosting

mig5 authored Feb 11, 2011 and mig5 committed Feb 11, 2011

Revert "#1016890 reapply contributed patch for fixing infinite loop - the reason it broke under Drush 4 was that I blew away our incorporation of the new cli context"

This reverts commit 0ae46243707c628a2a65dd3f69dac11c59586781.

It is breaking the upgrade path and any Migrate task, and possibly other stuff. See #1056864

mig5 authored Feb 06, 2011 and mig5 committed Feb 06, 2011

#1016890 reapply contributed patch for fixing infinite loop - the reason it broke under Drush 4 was that I blew away our incorporation of the new cli context

mig5 authored Feb 06, 2011 and mig5 committed Feb 06, 2011

Revert "#1016890 - a contributed fix for provision-save infinite loop when pulling options from stdin. happens to also fix cluster feature."

This reverts commit c214fe6063fdb7e9910b9a053f311c83a550827d.

mig5 authored Feb 05, 2011 and mig5 committed Feb 05, 2011

#1016890 - a contributed fix for provision-save infinite loop when pulling options from stdin. happens to also fix cluster feature.

anarcat authored Nov 25, 2010 and anarcat committed Nov 25, 2010

i got tired of stabbing my eyes with inline JSON output so I wrote a
very very simple command that just parses STDIN as a --backend output
command. this can be useful for debugging when calling backend commands
without thinking of removing --backend, or in my case, to pass data
through STDIN as JSON, but still have a proper output.

anarcat authored Nov 25, 2010 and anarcat committed Nov 25, 2010

i got tired of stabbing my eyes with inline JSON output so I wrote a
very very simple command that just parses STDIN as a --backend output
command. this can be useful for debugging when calling backend commands
without thinking of removing --backend, or in my case, to pass data
through STDIN as JSON, but still have a proper output.