Azure / Azure/bicep-types-az

Deployment of CosmosDB Account takes a lot of time

Open
#1,899 3 comments 0 reactions 0 assignees View on GitHub
No RP Github RP: Microsoft.DocumentDB
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

The bicep deployment time of the bicep file below is really high (westeurope). Even if it's already exists. Can this be investigated?

image

```
param location string
param cosmosDbAccountName string
param accountOfferType string

var locations = [
{
locationName: location
failoverPriority: 0
isZoneRedundant: false
}
]

resource cosmosDbAccount 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
location: location
name: cosmosDbAccountName
kind: 'GlobalDocumentDB'
properties: {
disableKeyBasedMetadataWriteAccess: true
databaseAccountOfferType: 'Standard'
consistencyPolicy: {
defaultConsistencyLevel: 'Session'
maxIntervalInSeconds: 5
maxStalenessPrefix: 100
}
backupPolicy: {
type: 'Continuous'
}
locations: locations
enableAutomaticFailover: true
}
tags: {
defaultExperience: 'DocumentDB'
}
}
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the deployment using the supplied Bicep resource declaration for Microsoft.DocumentDB/databaseAccounts@2023-04-15 in westeurope, including an already-existing account. Measure where the deployment spends time and investigate the Azure resource behavior; done means the cause is identified and a concrete fix or documented limitation is established.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.