Dynamic throttling option in OpenAI Studio should be marked as settable
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 44
- Avg merge
- 18h 53m
- Merged PRs (30d)
- 29
Description
Bicep version
Bicep CLI version 0.27.1 (4b41cb6d4b)
Describe the bug
Field dynamicThrottlingEnabled of resource Microsoft.CognitiveServices/accounts/deployments@2023-10-01-preview is settable and documented but marked as read-only.
To Reproduce
resource gpt 'Microsoft.CognitiveServices/accounts/deployments@2023-10-01-preview' = {
parent: cognitiveOpenai
name: gptModelFullName
sku: {
capacity: 80
name: 'Standard' // Pay-as-you-go
}
properties: {
dynamicThrottlingEnabled: true // Declared as read-only but can be set
model: {
format: 'OpenAI'
name: gptModel
version: gptVersion
}
}
}
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 with the definition for Microsoft.CognitiveServices/accounts/deployments@2023-10-01-preview and inspect how dynamicThrottlingEnabled is classified. Update the definition so the documented settable field is accepted in the Bicep resource example, then verify that the read-only diagnostic no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100