Ignoring of a specific property of a configuration works just fine.
For example: *:langcode will ignore the langcode property for all configurations. The problem is that the config diff shows reordering of that property and still tries to import the configuration, because Drupal now uses config schema to order keys for maps. (
https://www.drupal.org/node/2852557 →
)
Check the attached screenshot as an example.
Ignore a specific property of a configuration via Config Ignore and then make a config change - enable/disable random module. Then import configurations again and check the configuration status - the property is not changed, but the diff shows reordering and future config imports will keep trying to fix the order.
1. Determine whether this is reproducible by others.
2. Come up with a proper solution.
Closed: duplicate
3.0
Code
This is a known issue, see 🐛 drush config:import and drush config:status always report the configuration is different when ignoring specific keys (config sorting) Active