Permissions for bulk generate and update

I'm planning to work on this the upcoming Friday at Siili Solutions Drupal-contrib day.

I added a new merge request which can be tested. The merge request adds two new permissions to the module. The permission bulk update aliases is needed when accessing the pathauto.bulk.update.form route, and the permission bulk delete aliases when accessing the pathauto.admin.delete route. The tests and the description for the administer pathauto permission have also been updated to reflect the changes.

I discussed the implemented changes with a colleague and ended up modifying the merge request a bit. The route pathauto.bulk.update.form now required either the administer pathauto OR the bulk update aliases permission, and the route pathauto.admin.delete route requires either the administer pathauto OR the bulk delete aliases permission. This is because the administer pathauto permission indicates that a users should have access to everything pathauto related. The description for the administer pathauto permission has also been updated to reflect these changes.

Tested with the usual case in mind, being "I want to give my client the ability to create new path aliases but not give them anything related to pathauto, including bulk delete stuff"

Given the permissions as per attachment, the user with Content editor role now only sees the alias addition functionality in /admin/config/search/path - the "Bulk generate" and "Delete aliases" tabs are no longer there.
So works as I was hoping it to.

"Administer pathauto" or correct one of the new two permissions is now required to access those aforementioned two tabs.

PS. Only tested the functionality from Drupal UI using DrupalPod, did not review code.

Yeah, edge case. This will result in sites no longer having access to those pages, and I'm not sure if we should have an update function to ensure that things work as before, but I also agree that this doesn't match the documentation and is somewhat unintended.

It's a nice change that makes it easier to give non-admin users access to administer url aliases without the more complex and bulk create and delete sections, so lets go with it, will put something in the release notes that nobody will ready ;)

Automatically closed - issue fixed for 2 weeks with no activity.