Assigned
Status Update
No update yet.
Comments
mi...@sada.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
dh...@google.com
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
Description
Creating a reservation or commitments via the CLI or REST API currently do not support any type of `--test` flag. Any wrongful command could ultimately reserve and commit a wrong amount of resources to "production" and ultimately putting the procurer on the hook financially for those resources for 1 to 3 years (reaching out to support multiple times to cancel these commits/reservations seems unideal). Further issues could arise with the dependency of CUDs being applied to Reservations where --reservations-from-file=RESERVATIONS_FROM_FILE could be in bulk.
It would be great to have the ability to test the CLI or API call, returning the code of what would be created and how it would be assigned (in the case of Reservations + CUDS)
What you would like to accomplish:
I would like to programmatically test and than procure CUDS + Reservations with certainty that my code will not procure the specified amount.
How this might work:
Add --test to the CLI, and provide a human readable output that describes what would have been Reserved and/or committed to by running that command.
If applicable, reasons why alternative solutions are not sufficient:
No other solution found.
Other information (workarounds you have tried, documentation consulted, etc):
Tried reaching out to support to have them validate the command, but seems slow, inefficient, and sometimes misleading.