You are here

Home » API reference » Hosting 6.2 » hosting_example.service.inc » hostingService_example_basic

public function hostingService_example_basic::context_options in Hosting 6.2

Same name and namespace in other branches
  1. 7.4 example/example_service/hosting_example.service.inc \hostingService_example_basic::context_options()
  2. 7.3 example/example_service/hosting_example.service.inc \hostingService_example_basic::context_options()

Pass values to the provision backend when we call provision-save.

By selecting this type we already pass the '--example_service_type=basic' option to the command, which will load the matching provisionService class in the backend.

This backend class will be responsible for receiving and reacting to the options passed here.

Overrides hostingService::context_options

Related topics

Frontend/Backend Inter-process Communication
Aegir is based on a very important distinction between the "frontend" and the "backend". The frontend is the Drupal website that creates the user interface that people manipulate. The backend is (usually) a set a drush commands…

File

example/hosting_example.service.inc, line 211
Example service implementation for the hosting front end.

Class

hostingService_example_basic
An implementation of the example service type, registered with hook_hosting_service.

Code

public function context_options($task_type, $ref_type, &$task) {

  // REMEMBER TO CALL THE PARENT!
  parent::context_options($task_type, $ref_type, $task);
  $task->context_options['example_field'] = $this->example_field;
}