This problem was originally reported as a bug in Drupal core:
🐛
Update documentation for handling dots in the static_map plugin
Needs work
. On that issue, we decided that the problem comes from storing migrations as config entities, which is supported by the migrate_plus module.
Thanks to
#2293773: Field allowed values use dots in key names - not allowed in config →
, the Drupal configuration system does not allow periods (a.k.a. "dots") to appear in any configuration key. This causes problems when using the static_map process plugin to replace some.value.with.dots with something-else-without-dots.
Create a custom migration with a perfectly reasonable static_map usage to translate source strings to allowed_values:
field_cpu_bus_type:
plugin: static_map
source: BusType
bypass: true
map:
'PCIe 3.0': pcie_3_0
PCI: pci
...
The migration fails with
exception 'Drupal\Core\Config\ConfigValueException' with message 'PCIe 3.0 key contains a dot which is not supported.' in /var/www/example/docroot/core/lib/Drupal/Core/Config/ConfigBase.php:211
TBD
Here's one thought - permit map entries to be specified such that the map key is not a YAML key but rather a YAML value. E.g.:
field_cpu_bus_type:
plugin: static_map_plus
source: BusType
bypass: true
map:
-
key: 'PCIe 3.0'
value: pcie_3_0
PCI: pci
...
In other words, add a new process plugin that extends static_map and pre-process the map key.
None
None
Active
6.0
Miscellaneous
Hey!
I did some changes here to work, the code need to fix for the best practices, but it's working for me.
First you need to update the migration map with this format:
- plugin: static_map
keyvalue: TRUE
map:
- foo: 'bar'
- key: 'PCIe 3.0'
value: pcie_3_0
Accepts two ways to put the map items...