>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3548930. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !555 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The "Save config" action treats its incoming value as a literal (albeit token-replaced) array of config data. This is a problem if you want the action to create a config <em>entity</em>, since the entity system is presumably bypassed. It's also a UX problem, because you need to provide the <em>entire</em> config structure to ECA, rather than just the parts you care about.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>The action should be smart enough to detect if the config it's about to create is a config entity (it can figure this out by the config name prefix), and if so, it should interpret the value to set as a YAML array and pass it to Entity::create() or Entity::set(), depending on whether the entity already exists.</p>