New config architecture causes issues for managed config

Problem/Motivation

The config as generated by the 2.0.x module includes generated entity IDs, which are non-deterministic and prevent google_tag config being managed via settings.php by a config management system (like say Ansible)

I've made a first attempt at simply injecting config with a deterministic ansible-generated ID for the tag container entity, but Drupal seems to not pick that up. I'm kind of at a loss at this point. Suggestions that don't involve not managing config welcome?