#1263544 by GuyPaddock, Steven Jones: Fixed 'Can only throw objects in provision.config.inc, line 75'.

that warning

anarcat authored Aug 23, 2010 and anarcat committed Aug 23, 2010

we also make sure we return status in write()

Now that we are actually storing context objects in $this->context, standardize on $context everywhere. (ie: config classes when from $this->owner to $this->context.)

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

working provision-zone delete and create zone commands. generates the data store correctly, and uses locking.

still a work in progress.

Added key generation code and abstracted the configuration classes a bit more. There are now base http classes that handle the synching to remote servers.

A bevy of subtle fixes. Primarily #597750 because we no longer 'do' site id. Also fixed restore which left you with a broken site, and handled the fact that
the drush_config_file function would only give us the right value when we were bootstrapped to that level.

this meant we couldnt regenerate the site drushrc.php until we'd bootstrapped to drupal_configuration, which meant during restore it would always use the old values.

Also when the restore task finished, the save_site_config malarky would end up writing the old values over the correct ones.

the singular filesystem object now.

Sync is now a method of the server class, with a helpful method associated
to the services that redirect to the service's server.

Removed the provision_service function, and introduce service handler subscriptions in the environment objects.

Instead of provision_service('type') you now use d()->service('type') to access the service object.
The context object returned by d() now manages which context object's service to return, based
on the internally managed subscriptions.