Hello,
I'm encountering an issue with RedisDistributedLock. Currently, I am using a single Redis instance for multiple environments (such as dev and test). My goal is to use the same key in the TryAcquireLockAsync method but with different prefixes for each environment.
For example, in the application code, I have:
_distributedLockProvider.AcquireLockAsync(“DO_SOMETHING”);
However, in Redis, I need the keys to be environment-specific, like dev:DO_SOMETHING for the development environment and test:DO_SOMETHING for the test environment.
As a reference, in StackExchangeRedisCache, this is achieved as follows:
services.AddStackExchangeRedisCache(options =>
{
options.Configuration = “your_configuration”;
options.InstanceName = $"{Environment}:";
});
In this case, InstanceName serves as a prefix.
Would it be a good idea to consider adding an option for this in RedisDistributedSynchronizationOptionsBuilder during startup configuration?
Hello,
I'm encountering an issue with RedisDistributedLock. Currently, I am using a single Redis instance for multiple environments (such as dev and test). My goal is to use the same key in the TryAcquireLockAsync method but with different prefixes for each environment.
For example, in the application code, I have:
_distributedLockProvider.AcquireLockAsync(“DO_SOMETHING”);However, in Redis, I need the keys to be environment-specific, like dev:DO_SOMETHING for the development environment and test:DO_SOMETHING for the test environment.
As a reference, in StackExchangeRedisCache, this is achieved as follows:
In this case, InstanceName serves as a prefix.
Would it be a good idea to consider adding an option for this in RedisDistributedSynchronizationOptionsBuilder during startup configuration?