Skip to content
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

Get-AzRedisCache does not return minimumTlsVersion where "az redis show" does #9601

Closed
devblackops opened this issue Jul 11, 2019 · 0 comments · Fixed by #10510
Closed

Get-AzRedisCache does not return minimumTlsVersion where "az redis show" does #9601

devblackops opened this issue Jul 11, 2019 · 0 comments · Fixed by #10510
Assignees
Labels
Redis Cache Service Attention This issue is responsible by Azure service team.

Comments

@devblackops
Copy link

Description

The Redis properties exposed with Get-AzRedisCache are not consistent with what az redis show returns. In particular, I'm interested in minimumTlsVersion, which I can't find a way to return with the PS module.

Steps to reproduce

# Observe properties returned with PS module
Get-AzRedisCache -Name $name -ResourceGroupName $rg

# Observe properties returned with az cli
az redis show --name $name --resource-group $rg

Environment data

Name                           Value
----                           -----
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.18362 
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}        
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Module versions

ModuleType Version    Name
---------- -------    ----
Script     1.1.0      Az.RedisCache
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Redis Cache Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants