Description
We use the framework.cache.prefix_seed config in an app that has separate prod and staging environments to help further isolate some of our cache data. In our app, we've configured this to use an environment variable with a unique value per environment. However, I recently noticed that one of our caches looked to be getting shared across environments, and after digging, I found this was because the config value is written to the cache.prefix.seed container parameter that's only used as a build (compile) parameter. This resulted in our build step unexpectedly using the env var's default value and our deployment platform env vars having no effect.
To keep others from making this mistake, it might be good to note that this config is only used at compile time.