-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Redis CLI does not Support Geo-Replication Configuration #9286
Comments
CLI for azure redis cache does support replication between multiple regions. |
@alfantp - I'm still getting the error which seems to indicate otherwise. Here in more detail:
(redis #1)
(redis #2)
All of these give the same type of error:
NOTE: No matter what permutations of the command, the indication is always that the primary redis instances is being looked for under the resource group of the secondary redis cache.
Same error:
|
Note: Geo-replication using Powershell works smoothly, implementation also appears to be simpler than azure cli, unexpectedly .
|
Hello @archmangler , when resource ID is mentioned in azure, it generally refers to the ARM resource id, which you posted in the beginning of your post. Design principles for CLI mentions using a single parameter to accept either ARM Resource ID or resource name for a supporting resource in an operation: |
Thanks for looking into the @alfantp. Since you have verified the command is working as intended and that the functionality is supported, I will close this issue. @archmangler supplying |
Describe the bug
The azure cli command for configuring redis cache geo-replication only works when the redis instances are a) in the same resource group and therefore b) in the same region. Effectively, this means geo-replication cannot be configure via az cli at the moment since functionality is limited to geo-replication within a single region.
The azure cli documentation for configuring redis cache geo-replication is not clear on which resource-group should be specified (the resource group of the primary redis instance or the secondary?). Unless this implies that both instances should be in the same resource group (which is not clear from the documentation).
To Reproduce
Expected behavior
Azure CLI should allow Geo-replication to be configured between redis caches in separate regions and separate resource groups.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (
az --version
) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)Additional context
When the instances are in the same resource group and same region, replication configuration works. However, that does not achieve our use-case. Putting the instances into separate regions requires separate resource groups. However, once we use separate resource groups the az cli command for setting up replication fails, unwilling to accept either resource group as an argument. So it seems the only conclusion to deduce from that is that the az cli only supports geo-replication within a region and within the same resource group and therefore is not actually "geo" replication, but just "replication"
The text was updated successfully, but these errors were encountered: