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

Storage account create min TLS version has TLS1_3 on help but this is not a valid option in Azure #30022

Open
evertonspader-tomtom opened this issue Oct 2, 2024 · 3 comments
Assignees
Labels
Auto-Assign Auto assign by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage az storage
Milestone

Comments

@evertonspader-tomtom
Copy link

Describe the bug

Azure CLI for creating a storage account suggests that a TLS1_3 option is available for --min-tls-version, but that is not an available version.

Related command

  az storage account create --subscription $SUBSCRIPTION \
    -g $RESOURCE_GROUP_FOR_STORAGE_ACCOUNT \
    -n $STORAGE_ACCOUNT \
    -l $REGION \
    --sku Standard_LRS \
    --kind StorageV2 \
    --min-tls-version TLS1_3

Errors

ERROR: (FeatureNotSupported) Feature MinimumTlsVersion 1.3 is not supported.
Code: FeatureNotSupported
Message: Feature MinimumTlsVersion 1.3 is not supported.

Issue script & Debug output

ERROR: (FeatureNotSupported) Feature MinimumTlsVersion 1.3 is not supported.
Code: FeatureNotSupported
Message: Feature MinimumTlsVersion 1.3 is not supported.

Expected behavior

The option for TLS 1.3 shouldn't be described in the help instructions of the command.

Environment Summary

azure-cli                         2.64.0

core                              2.64.0
telemetry                          1.1.0

Additional context

Azure Portal also doesn't offer the TLS 1.3 option:
image

@evertonspader-tomtom evertonspader-tomtom added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 2, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Oct 2, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Oct 2, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 2, 2024
@yonzhan yonzhan added this to the Backlog milestone Oct 2, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 2, 2024
@calvinhzy
Copy link
Member

Hi @evertonspader-tomtom, might be a regression from service side since it was working previously
image

@calvinhzy calvinhzy added the Service Attention This issue is responsible by Azure service team. label Oct 8, 2024
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@yonzhan yonzhan removed the Azure CLI Team The command of the issue is owned by Azure CLI team label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage az storage
Projects
None yet
Development

No branches or pull requests

4 participants