ConfigurationGenerator(/vendor/netgen/admin-ui-bundle/bundle/Installer/Generator/ConfigurationGenerator.php) is not setting the 'cache_service_name' attribute to '%cache_pool%' in method generate.
Consequently if NetgenAdminUIBundle is used with Legacy Bridge:
So if a content is published from Legacy Admin UI, keys in pool 'cache.app' will be purged, leaving 'cache.redis' keys untouched and EZ REST API will return stale data.
Alternatively state in README.md that such attribute must be set to avoid the above problems.
ConfigurationGenerator(/vendor/netgen/admin-ui-bundle/bundle/Installer/Generator/ConfigurationGenerator.php) is not setting the 'cache_service_name' attribute to '%cache_pool%' in method generate.
Consequently if NetgenAdminUIBundle is used with Legacy Bridge:
The Legacy Admin Ui will comunicate with symfony's cache pool 'cache.app'
Whereas EZ REST API will comunicate with symfony's cache pool 'cache.redis'
So if a content is published from Legacy Admin UI, keys in pool 'cache.app' will be purged, leaving 'cache.redis' keys untouched and EZ REST API will return stale data.
Alternatively state in README.md that such attribute must be set to avoid the above problems.