function Boot::bootstrap_init_phases

8.0.x Boot.php Boot::bootstrap_init_phases()
7.x Boot.php Boot::bootstrap_init_phases()
master Boot.php Boot::bootstrap_init_phases()

Lists the key bootstrap phases where Drush should stop and look for more commandfiles. In Drupal, Drush first does just a preflight, and if the selected command is not found after preflight, then a full bootstrap is done.

Return value

array of PHASE indexes.

2 calls to Boot::bootstrap_init_phases()
BaseBoot::bootstrap_and_dispatch in lib/Drush/Boot/BaseBoot.php
Main entrypoint to bootstrap the selected CMS and execute the selected command.
BaseBoot::bootstrap_and_dispatch in lib/Drush/Boot/BaseBoot.php
Main entrypoint to bootstrap the selected CMS and execute the selected command.
2 methods override Boot::bootstrap_init_phases()
DrupalBoot::bootstrap_init_phases in lib/Drush/Boot/DrupalBoot.php
The phases where Drush will look to see if new commandfiles have been defined. For Drupal, we first do a preflight, and if a command is not found at that point, we next attempt a full bootstrap. If a command is found after preflight, then…
EmptyBoot::bootstrap_init_phases in lib/Drush/Boot/EmptyBoot.php
Lists the key bootstrap phases where Drush should stop and look for more commandfiles. In Drupal, Drush first does just a preflight, and if the selected command is not found after preflight, then a full bootstrap is done.

File

lib/Drush/Boot/Boot.php, line 59

Namespace

Drush\Boot

Class

Boot
Defines the interface for a Boot classes. Any CMS that wishes to work with Drush should extend BaseBoot. If the CMS has a Drupal-Compatibility layer, then it should extend DrupalBoot.

Code

function bootstrap_init_phases();