qos-booking-and-assignment: A new endpoint needed to modify device count in an active booking #67
Description
Problem description
The current API lacks the functionality to modify the device count of an active booking. Users who initially booked a specific number of devices may find during the operation that they need to scale up or down. For instance, a user who booked 10 devices may realize they need two more, or they may want to release some to save on cost. Without this functionality, users must cancel and re-book, leading to service disruption, lost time, and poor user experience. We already support release operation. This operation will help reduce the number of devices that are not needed and can help substituate with new devices provisioned. While a release operation exists, it only frees up unneeded devices and does not update the total device count in the booking or associated cost profile, leading to inaccurate billing.
Possible evolution
A new API endpoint is required to support dynamic changes to the number of devices within an active QoS booking. This modification should accommodate both increasing the device count (e.g., adding more devices during an operation) and decreasing it (e.g., releasing unnecessary devices to save costs). This new operation is part of the Booking section of the API and will directly impact the cost profile of the booking.
If the operator has already allocated resources and cost profile can't be modfied then decreasing the device count will fail. It has not effect. In a simillar situation, if the operator could not allocate resources to add more devices to get the required QoS, this operation again will fail. In both cases, appropriate error code will be returned.
Alternative solution
Additional context