Closed Pynop closed 5 years ago
hmm.. I just created a TableAPI cosmosaccount using PS - azurerm 6.12 and it appears to work fine?
$TableDBAcc.Properties
provisioningState : Succeeded documentEndpoint : https://lukeb-tableapi.documents.azure.com:443/ tableEndpoint : https://lukeb-tableapi.table.cosmosdb.azure.com:443/ ipRangeFilter : enableAutomaticFailover : False enableMultipleWriteLocations : False isVirtualNetworkFilterEnabled : False virtualNetworkRules : {} EnabledApiTypes : Table, Sql databaseAccountOfferType : Standard consistencyPolicy : @{defaultConsistencyLevel=Eventual; maxIntervalInSeconds=5; maxStalenessPrefix=100} configurationOverrides : writeLocations : {@{id=lukeb-tableapi-australiaeast; locationName=Australia East; documentEndpoint=https://lukeb-tableapi-australiaeast.documents.azure.com:443/; provisioningState=Succeeded; failoverPriority=0}} readLocations : {@{id=lukeb-tableapi-australiaeast; locationName=Australia East; documentEndpoint=https://lukeb-tableapi-australiaeast.documents.azure.com:443/; provisioningState=Succeeded; failoverPriority=0}} failoverPolicies : {@{id=lukeb-tableapi-australiaeast; locationName=Australia East; failoverPriority=0}} capabilities : {@{name=EnableTable}}
@Pynop The generic PowerShell celets for creating resources are just using the public api for creating resources, so this behavior seems by design. It would be nice if there were typed cmdlets for Cosmos DB.
Description
When I create a CosmosDB account of type Table manually (using Azure Portal) I get a fully operable account. But when I do the same with a PS cmdlet I get an account in preview mode. That is identified by a corresponding message section in Azure Portal when I observe the resources created with PS. Here's a link to MS docs, pay attention to the feedback section in the bottom of the page. https://docs.microsoft.com/en-us/azure/cosmos-db/scripts/create-table-database-account-powershell?toc=%2fpowershell%2fmodule%2ftoc.json It's not only me who observed the issue. But the solution (use cloud shell instead) didn't work in my case - the account created using the cloud shell at Azure Portal is also in a preview mode. I also ran the cmdlet with -Debug option and "capabilities" array in the response from Azure is empty though in my understanding it should contain "EnableTable".
Script/Steps for Reproduction
Module Version
Environment Data
Debug Output