system.action configs have wrong dependency to domain

Sorry for the late respone. The config name is not the problem, those are created as you say domain_access_add_action.<ID>
the problem is within the dependencies of the config.

status: true
dependencies:
  config:
    - config.<ID>
  module:
    - domain_access
id: domain_access_add_action.<ID>
label: 'Add selected content to the <LABEL> domain'
type: node
plugin: domain_access_add_action
configuration:
  domain_id: <ID>

Still not able to pinpoint where the problem is

Problem does not exist in website installed with Drupal 9.5.2 and domain + domain_access 1.0.0-beta6
Problem exists in website installed with Drupal 9.5.2 and domain + domain_access 1.x-dev

So there must be some change between the 1.0.0-beta6 and the current dev branch.

Thanks @agentrickard to point me in the correct direction.
I found the commit that changed the behaviour of the actions config.

In version 8.x-1.0-beta6 the config dependencies are calculated and the config prefix was domain.record
In version 8.x-1.x the config dependencies are calculated with a different method and the config prefix is config

Changing the code back to getConfigPrefix gives the correct config dependency.

Created a MR with the needed code change.

Looks good. Running tests against 10.x.

I wonder why we made this change -- did you find the original issue or just the commit?

I found the corresponding issue for the commit. The commit references to MR19 and that points to #3283843: Run drupal check and fix issues →

Applied the patch

1. Created a new domain.
2. Exported the configurations.
3. The system.action files were found having correct config name, under dependencies.

Hence, marking it as RTBC.
Thanks @tim-diels

Thanks all! I will do a beta release this week.

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

I tested the patch on D10.0.2 with Domain 2.0.x-dev, it's OK for me too. Thanks @tim-diels !

Steps:

1. Add patch to composer = https://git.drupalcode.org/project/domain/-/merge_requests/32.patch
2. Apply the patch
3. Remove and recreate the existing domain in backend
4. Export config
5. The config files system.action.domain_access_*.yml have updated dependencies, and the import is done correctly

Hey all,

This problem still persist (on version 2.0.0beta 2).
The patch correction is already added on this version, but the YML still don't have "domain_id".

When I export my YML is like this:

dependencies:
  config:
    - domain.record.

after ".record." should be domain ID as it mention on this post.

Any idea about it?

Thanks in advance.

I can confirm this.

On drupal 10.2.4 with domain 2.0.x-dev there are after enabling domain_access four yml-files with an empty record-id.

system.action.domain_access_all_action
system.action.domain_access_edit_all_action
system.action.domain_access_edit_none_action
system.action.domain_access_none_action

drush cim on staging fails

Hi,
I have the same problem, I think we need to open a ticket again.
Drupal 10.3.0,
Domain Access: 2.0.0-beta2

The problem does appear again

This issue is closed. Please see 💬 Configuration system.action.domain_access_none_action depends on the domain.record configuration that will not exist after import. Active for a resolution.