we add safety check so that we don't get caught running d() before
drush is fully initialized. otherwise, the proper services hooks may
not be properly declared and found by drush, so the object cache
($instances) would be initialised with incomplete data.

it is possible that more initialisation we need happens after
DRUSH_BOOTSTRAP_NONE, but this is already better than nothing.

it took me and ergonlogic three freaking full days of headbanging on
keyboards to figure that stuff out.

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.

mig5 authored Jan 05, 2011 and mig5 committed Jan 05, 2011

Revert "#1014638 - add compatability for Drush 4, where the 'options' context has been renamed to 'cli'"

This reverts commit 61585e53a2783c2aa85f14e20ee262768cf6a48d.

The Environment classes were left over from development. Rename them to provisionContext_$x and move them to separate includes.