cfo

Override field values of content entities via settings.php and it has no UI.

Why to do this:

If you have config or private information managed via content entities you you may want to protect them or just alter them on testing workflows via settings.php e.g. with ".env" variables.

Good to know

Currently only developed and tested with single value string fields.
Primary on hook_entity_storage_load the field value will be copied to new pseudo field (prepfixed with "cfo_") and replaced by configured value. Be care of large fieldnames because there is a max length. If there is a need we can add settings for specifiying the "helper" fieldname. In any case everything should be tested before using on productive sites.

You need to know the uuid of the entity or you can use a serial entity ID but you need alos need the basic field for this like "nid" on nodes (see example below).

Config example in settings.php

$settings['cfo.settings']['node']['items']['nid']['1'] = [
  'title' => 'Hello world!'
];

This is similar to Configuration overrides like

$config['system.site']['name'] = 'My Drupal site';