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

Microsoft.DocumentDB databaseAccounts APi Version in gov not updated #30715

Closed
bryanberardi opened this issue Jan 24, 2025 · 5 comments
Closed
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. CosmosDB az cosmosdb customer-reported Issues that are reported by GitHub users external to the Azure organization. Possible-Solution Service Attention This issue is responsible by Azure service team. Similar-Issue

Comments

@bryanberardi
Copy link

Describe the bug

Failing to run az cosmosdb commands in AzureUsGov when using Microsoft.DocumentDB databaseAccounts through the cli, as the latest version sent by client is 2024-11-15 but latest available in Gov is 2024-09-01-preview. We can't specify the api version and have to fully downgrade the cli to run the needed commands.

Related command

az cosmosdb sql database list --account-name {} --resource-group {}

Errors

No registered resource provider found for location 'usgovvirginia' and API version '2024-11-15' for type 'databaseAccounts'. The supported api-versions are ...several other version..., 2024-09-01-preview'. The supported locations are 'usgovarizona, usgovtexas, usdodcentral, usdodeast, usgovvirginia'.

Issue script & Debug output

az cosmosdb sql database list --account-name {} --resource-group {}

Expected behavior

Should be able to run az cosmosdb commands using latest az cli without apiversion errors

Environment Summary

azure-cli: 2.68.0

Additional context

Similar previous issue found: #17844

@bryanberardi bryanberardi added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 24, 2025
Copy link

Hi @bryanberardi,

This is a known issue.

Please follow #23985 (comment) to get temporary workaround.

If you feel that further discussion is needed, please add a comment with the text /clibot unresolve to reopen the issue.

@azure-client-tools-bot-prd azure-client-tools-bot-prd bot added the Auto-Resolve Auto resolve by bot label Jan 24, 2025
@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 Jan 24, 2025
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 24, 2025

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 Service Attention This issue is responsible by Azure service team. CosmosDB az cosmosdb labels Jan 24, 2025
Copy link

Here are some similar issues that might help you. Please check if they can solve your problem.


Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

You can unblock yourself by using the apiVersion 2021-04-15. We have not publicly announced it yet, but it is rolled out in all regions and contains everything that exists in 2021-03-15.

Reference:

Solution 2:

A workaround specific to these commands is setting the profile version:

az cloud set --name AzureUSGovernment --profile 2020-09-01-hybrid

Reference:

Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @kushagraThapar, @simplynaveen20.

1 similar comment
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @kushagraThapar, @simplynaveen20.

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 Auto-Resolve Auto resolve by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. CosmosDB az cosmosdb customer-reported Issues that are reported by GitHub users external to the Azure organization. Possible-Solution Service Attention This issue is responsible by Azure service team. Similar-Issue
Projects
None yet
Development

No branches or pull requests

2 participants