Show permissions defined by a module after pm-enable, and in pm-info

Slight improvement: print nothing in pm-enabled if there are no permissions defined in the module.

You are right, it is not necessary to re-bootstrap the site to get an accurate list of permissions after enabling a module.

Here is an improved patch that supports D7, and does not incorrectly report "no permissions defined" for disabled modules. Since it is not possible to call hook_perm / hook_permission unless the module is enabled, pm-info merely omits the "Permissions defined" display when the module is not enabled. I didn't think it was a good idea to try to include the right file or "fake-enable" the module just to get this info.

I agree that it would be a good idea to bring drush_role into core. This patch also still needs unit tests.

I don't think that Drush should print URLs at pm-enable time; it would be okay to put this information in pm-info, though.

Created #1649598: Bring drush_role into Drush core for bringing drush_role into Drush core.

Re-rolled now that drush_role is in core.

I can give you my impression. If you are enabling a module where you have memorized the permissions it defines, or don't care what the permissions are, then the extra output is fairly minimal, and easily ignored. A more useful case, though, is when enabling a new module, Drush will now immediately inform you of the permissions available to be set. This allows you to easily follow up with something like drush rap editor 'new permission'. It's more efficient to set permissions up front like this than to put it off until the test phase, so I think this is a win.

Here's a new patch with tests. Note that this also includes a test for pmi, and therefore also includes --pipe output for pmi. I re-factored some of the core-status output code into drush_format so that I could re-use it here.

Slight refinement of drush_format. The difference between #9 and #10 is negligible for this patch, but will be important for a follow-up patch that I'll be submitting after this one is put to bed.

No feedback; shall we go ahead and commit #10, either with or without the bit that actually outputs the permission names after pm-enable (per your preference)? Even without the main functionality of the patch, the other improvements, such permissions listed in pm-info, and unit test for pm-info, should go in.

Here is the part that would be removed if output after pm-enable is not desired.

 --- a/commands/pm/pm.drush.inc
+++ b/commands/pm/pm.drush.inc
@@ -892,9 +892,14 @@ function drush_pm_enable() {
   // Inform the user of final status.
   $result_extensions = drush_get_named_extensions_list($extensions);
   $problem_extensions = array();
+  $role = drush_role_get_class();
   foreach ($result_extensions as $name => $extension) {
     if ($extension->status) {
       drush_log(dt('!extension was enabled successfully.', array('!extension' => $extension->name)), 'ok');
+      $perms = $role->getModulePerms($extension->name);
+      if (!empty($perms)) {
+        drush_print(dt('!extension defines the following permissions: !perms', array('!extension' => $extension->name, '!perms' => implode(', ', $perms))));
+      }
     }

Yep, works for all three supported versions of Drupal. Committed; thanks.