Pubsub model does not support multiple deployments using the same Redis instance

[MikeGoldsmith]

Prior to Refinery 2.7.0, it was possible to utilise a single Redis instance with multiple Refinery deployments (eg dev, staging, test). From Refinery 2.7.0 and onwards, it is no longer possible because Redis' pubsub model does not separate communicator based on selected Database ID.

Versions

• Refinery: 2.7.0 onwards

Steps to reproduce

1. Upgrading to Refinery 2.7.0 or later

Additional context

There is a deprecated Prefix configuration option that could be reintroduced to be used with the topic names used to subscribe and publish messages to.

For example, no prefix would see no change in topic name, eg {topic-name}. If the test prefix was provided, the topics would build topic names like test:{topic-name}.

[Graham-Russell-Forter]

This is affecting us - we'd like to use one ElastiCache for multiple Refinery deployments for environment.