conductor-oss
[FEATURE]: Make redis key space domain customizable
Please read our contributor guide before creating an issue.
Also consider discussing your idea on the discussion forum first.
Describe the Feature Request
Make redis key space domain customizable, there by allowing multi-tenant software to namespace | isolate their data in the same redis db. This primarily applies to the hash bucket keys.
Describe Preferred Solution
In com.netflix.conductor.redis.dao.BaseDynoDAO instead of the domain being a member variable, access from the property instance on demand. A derived bean instance of ConductorProperties (already a member of BaseDynoDAO) will be able to access the customized domain seamlessly.
Describe Alternatives
Considered other fields like stack, however key space domain is the most meaningful customization for tenant isolated hash buckets
@maggmanu77 based on @v1r3n comment above regarding PR #221 has this issue been resolved?
