Azure / Azure/bicep-types-az

Microsoft.Capacity/reservationOrders@2022-03-01' not working because Microsoft.Capacity/calculatePrice is not supported

Open
#2,052 8 comments 2 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

**Bicep version**
Bicep CLI version 0.6.18 (46dd19e8eb)

**Describe the bug**
when using 'Microsoft.Capacity/reservationOrders@2022-03-01' to create a reservation we are getting a badrequest with the following error: ""Session timed out - Call CalculatePrice again and provide the new Reservation Order ID for purchase""

This is because Microsoft.Capacity/reservationOrders does not create a reservation order id, when using the api you would first run Microsoft.Capacity/calculatePrice to create a calculated price and use that order id in the reservation orders.

the existence of Microsoft.Capacity/calculatePrice is not mentiond in bicep, when trying to build the Microsoft.Capacity/calculatePrice call in bicep it fails with a scoping error " does not have permission to perform action 'Microsoft.Capacity/calculatePrice/write' at scope '/providers/Microsoft.Capacity/calculatePrice/{bicepName}'.'."}" becasue bicep uses the name value in its scope and this is not needed in the calculation price. becasue of this Microsoft.Capacity/reservationOrders@2022-03-01' is broken.
**To Reproduce**
just try to deploy Microsoft.Capacity/reservationOrders@2022-03-01'

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing Microsoft.Capacity/reservationOrders@2022-03-01 with Bicep CLI 0.6.18, then compare it with the Microsoft.Capacity/calculatePrice entry point described in the report. Done means the reservation deployment no longer fails because the required reservation order ID or calculatePrice scope is unsupported.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.