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.

Sign up for GitHub

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

Jump to bottom

[AVM Module Issue]: Cannot only specify throughput at container level or database level #1226

Closed
1 task done
bryansan-msft opened this issue Mar 9, 2024 · 1 comment · Fixed by #1223
Closed
1 task done

[AVM Module Issue]: Cannot only specify throughput at container level or database level #1226

bryansan-msft opened this issue Mar 9, 2024 · 1 comment · Fixed by #1223
Assignees
@bryansan-msft
Labels
Class: Resource Module 📦 This is a resource module Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Feature Request ➕ New feature or request

Comments

@bryansan-msft
Copy link
Contributor

bryansan-msft commented Mar 9, 2024 •
edited
Loading

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/document-db/database-account

(Optional) Module Name if not listed above

No response

(Optional) Module Version

No response

Description

Right now, database and container throughput default value is 400 RU in the current version. Making impossible to only specify throughput at container or database since even if you specify that you want a database of 1000 RU the container will still default to 400 thus generating unnecesary costs

(Optional) Correlation Id

No response
@bryansan-msft bryansan-msft added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Mar 9, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 Reply has been added to issue, maintainer to review Type: Feature Request ➕ New feature or request labels Mar 9, 2024
@github-actions github-actions bot added the Class: Resource Module 📦 This is a resource module label Mar 9, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Mar 9, 2024

@bryansan-msft, thanks for submitting this issue for the avm/res/document-db/database-account module!

A member of the @azure/avm-res-documentdb-databaseaccount-module-owners-bicep or @azure/avm-res-documentdb-databaseaccount-module-contributors-bicep team will review it soon!

@bryansan-msft bryansan-msft changed the title [AVM Module Issue]: Database throughput is always set even if you didn't set anything, which generates unnecessary costs [AVM Module Issue]: Cannot only specify throughput at container level or database level Mar 9, 2024
@bryansan-msft bryansan-msft linked a pull request Mar 9, 2024 that will close this issue
fix: Force partition key parameter and Fix hierarchical partition key deployment and analytical store enablement #1223
Merged
11 tasks
@bryansan-msft bryansan-msft mentioned this issue Mar 11, 2024
Merged
11 tasks
@matebarabas matebarabas removed Needs: Triage 🔍 Maintainers need to triage still Needs: Attention 👋 Reply has been added to issue, maintainer to review labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bryansan-msft bryansan-msft

Labels
Class: Resource Module 📦 This is a resource module Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Feature Request ➕ New feature or request
Projects
AVM - Module Issues
Status: Done
Bicep
Archived in project
Milestone
No milestone
2 participants
@matebarabas @bryansan-msft