Skip to content

Commit c27e14b

Browse files
committed
feature #35890 [Cache] give control over cache prefix seed (Tobion)
This PR was merged into the 5.2-dev branch. Discussion ---------- [Cache] give control over cache prefix seed | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | | License | MIT | Doc PR | Reopened #35723 for master. The configurable cache prefix seed does not give full control over the cache prefix because the container class is added to the prefix in any case. This is a problem because the container class contains the app env name. We use different app environments for different deployment targets (dev and test). We want dev and test to use the same redis cache. But this is impossible to achieve because even setting the cache prefix seed does not accomplish this. Commits ------- 6681b92524 [Cache] give control over cache prefix seed
2 parents d0fd09c + f66bd08 commit c27e14b

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

Tests/DependencyInjection/SecurityExtensionTest.php

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -366,6 +366,7 @@ public function testRememberMeCookieInheritFrameworkSessionCookie($config, $same
366366
$container->setParameter('kernel.bundles_metadata', []);
367367
$container->setParameter('kernel.project_dir', __DIR__);
368368
$container->setParameter('kernel.cache_dir', __DIR__);
369+
$container->setParameter('kernel.container_class', 'app');
369370

370371
$container->loadFromExtension('security', [
371372
'firewalls' => [

0 commit comments

Comments
 (0)