https://www.drupal.org/node/2092643
_permission: A permission string (e.g., _permission: 'access content'). You can specify multiple permissions by separating them with ',' (comma) for AND logic or '+' (plus) for OR logic. E.g., _permission: 'access content,access user profiles' Module-specific permission strings can be defined in my_module.permissions.yml. See https://www.drupal.org/node/2311427 for details.
_role: A specific Drupal role, eg. 'administrator'. You can specify multiple ones via "," for AND and "+" for OR logic. Note that, since the roles available may differ between sites, it's recommended to use permission based access restriction when possible.
_module_dependencies: Optionally use this key to specify one or more modules that are required to serve this path. You can combine module names with a + (plus) for an AND relationship or , (comma) for an OR relationship. For example, _module_dependencies: 'node + search' means both node and search are needed, _module_dependencies: 'node, search' means either node or search are needed. If your module already depends on other modules for its behaviour (via info.yml dependencies), there is of course no need for specifying the dependency here as well; however for optional dependencies, where routes are provided only if those optional dependent modules are also enabled, this is a useful option.
Comments
Comment #2
pfructuoso commentedI don't think it's a novice issue as it'll involve backward compatibility and probably have to change several tests.
Comment #3
pfructuoso commentedComment #13
cilefen commentedI am closing this support request because there have been no recent comments.
The Drupal Core issue queue is not the ideal place for support requests. Consider other sources of support.