Add configurable prefixes to Redis Tracker and Lock stores #6498
Labels
area:rasa-oss 🎡
Anything related to the open source Rasa framework
type:enhancement ✨
Additions of new features or changes to existing ones, should be doable in a single PR
Description of Problem:
Currently Rasa does not allow using the same Redis instance for the TrackerStore and the LockStore because they use the same keys which overwrite each other or Rasa requires separate logical Redis DBs which most Redis services do not support multiple logical DBs (only
select 0
supported).Related issues:
Overview of the Solution:
Allow a new parameter in
endpoints.yml
to specify an alphanumeric prefix which is prepended to all keys for the given (Lock|Tracker)Store. The prefix should be optional for compatibility therefore the configurable prefix will be prepended as eitherprefix:lock:<senderid
orprefix:tracker:<senderid>
. The lock and tracker keys will not collide and a given Redis instance can be used by more than one conversation tracker.Definition of Done:
Tests are addedExisting tests provide sufficient coverage with minor changes.The text was updated successfully, but these errors were encountered: