Define permission dependencies

The MR uses the node module as a model.

Testing steps:

1. Install Drupal 10.2.x with the Standard profile.
2. Enable search_api_autocomplete and search_api_db_defaults (and dependencies).
3. Enable "Search content" on Default content index > Autocomplete (/admin/config/search/search-api/index/default_index/autocomplete).
4. Assign the "Use autocomplete for the Search content search" permission to the Content editor role on /admin/people/permissions/module/search_api_autocomplete.
5. Go to /admin/config/development/configuration/single/export and export the config for the Content editor role.

In the last step, I see the following dependencies:

dependencies:
  config:
    - node.type.article
    - node.type.page
    - search_api_autocomplete.search.search_content
    - taxonomy.vocabulary.tags
  module:
    - comment
    - contextual
    - file
    - node
    - path
    - search_api_autocomplete
    - system
    - taxonomy
    - toolbar

That is, the role correctly depends on the search_api_autocomplete.search.search_content configuration.

To complete the test,

1. Switch to the 8.x-1.x branch.
2. Remove the permission from the Content editor role.
3. Clear caches.
4. Restore the permission.
5. Export the role config.

Now I see these dependencies:

dependencies:
  config:
    - node.type.article
    - node.type.page
    - taxonomy.vocabulary.tags
  module:
    - comment
    - contextual
    - file
    - node
    - path
    - search_api_autocomplete
    - system
    - taxonomy
    - toolbar

The module is listed but not the search config.

@drunkenmonkey:

Please consider giving issue credit to those who commented on 🐛 "Adding non-existent permissions to a role is not allowed." exception is thrown for profile installations Needs work : @codebymikey and @smustgrave.

drunken monkey → made their first commit to this issue’s fork.

Thanks a lot for reporting this problem and already providing the correct fix!
Seems this has been available for ages (since Drupal 9.3), so should be no problem increasing our version requirement to that. Anyone still on 9.2 is hardly gonna keep this module up to date.
I’ve also added a one-line test to make sure this works correctly.

Please test/review and I can merge.

@drunken monkey:

Thanks for catching the version requirement. BTW, Drupal 9.3 also introduced the module-specific permissions form that I mentioned in Step 4 of my testing instructions (Comment #3).

I reviewed the changes, and they look good. To keep myself honest, I checked the test to see where the magic string "muh" is introduced.

I repeated the test from Comment #3 and got the same result.

The other issue brought this bug to my attention. Reporting a bug is an important step in getting it fixed, even though the initial analysis was incomplete. I reviewed the issue that introduced permission dependencies, and I wrote the change record, so I did not need much help in figuring it out.

Good to hear, thanks for reporting back!
Merged. Thanks again!

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