Using Verbose Output for Debugging Drupal Recipes

Brian Perry shared insights on the usefulness of verbose output when applying Drupal Recipes in a recent blog post. He explained that while automating the application of related recipes in a shell script, he encountered an issue where one recipe did not apply cleanly. To debug the problem, he used the `-v` flag with the `drush recipe` command, which provided detailed output beyond the standard confirmation message. The verbose output included installed modules, dependencies, and various bootstrap phases of Drupal’s execution, making it a faster alternative to manually reviewing source code or module pages in the admin UI. Brian noted that `-vv` provides similar information while `-vvv` adds more details that he did not find particularly useful. However, none of these options offer debug output for configuration actions, which he identified as a potential area for improvement. He concluded that using the `-v` flag by default when applying new recipes provides a clearer understanding of what is being added to a Drupal site.