Cannot update continuous backup mode and other properties at the same time when run bicep on area with an existing Cosmos database.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 44
- Avg merge
- 18h 53m
- Merged PRs (30d)
- 29
Description
Describe the bug
Cannot update continuous backup mode and other properties at the same time. When running bicep in an area with an existing Cosmos database.
To Reproduce
Run pipeline
Additional context
resource poiCosmosAccount 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
name: toLower(cosmosName)
kind: 'GlobalDocumentDB'
location: location
tags: defaultTags
properties: {
databaseAccountOfferType: 'Standard'
locations: [ { locationName: location, failoverPriority: 0 } ]
ipRules: ipRules
backupPolicy: {
type: 'Continuous'
continuousModeProperties: { tier: 'Continuous7Days' }
}
}
}
Is there any way to fix this? As you can see I'm using the latest version: 2023-04-15
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the reported pipeline against an area with an existing Cosmos database using the Microsoft.DocumentDB/databaseAccounts@2023-04-15 declaration. Then locate the relevant type definition or validation entry point and verify that continuous backup mode and other properties can be updated together. No repository file or test is named, so locating the affected definition is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100