Closed tomasrelai closed 3 years ago
i updated the sdk to take an enum value for engine size, this does mean that if we add sizes to the API that we will need to update the sdk, but i think this is the right tradeoff, esp as we want to move away from explicitly managing engines in most cases.
Note: This issue has been migrated to https://relationalai.atlassian.net/browse/RAI-3716.
This link is only accessible to employees of RelationalAI.
If I use a bogus size string in, say,
create_compute
, the error comes back as an HTTP error.We should consider having an enumerated type for those strings, or perhaps validating them before sending out the request? It would also be nice to list the allowable strings (or types) in the docstring.
On the other hand, if the cloud environment, say, adds more sizes, if those are built into the library, then a new release of the library would be needed to support the new sizes. Wondering if there could be a separate API call that lists the valid sizes, then --- called once when the library is initialized / before the first request is made, perhaps.