Repository navigation
Conversation
| description: Filter sizes to those with a given GPU fabric setting | ||
| required: false | ||
| schema: | ||
| type: boolean |
There was a problem hiding this comment.
gpu_fabric is not on the size/gpu_info response, should we document it there or clarify what true/false means here?
There was a problem hiding this comment.
fabric is a property of some 8x GPU sizes. it's to do with the networking between GPUs. customers who use this feature are very aware of it.
currently this information is baked into the slug name, which is a bit suboptimal. We could also supplement the gpu object to have a fabric boolean. I'll make a note here to bring this idea up with the team at standup.
There was a problem hiding this comment.
a fabric boolean has been added to the GPU info object
| description: Filter sizes with an inclusive minimum hourly price (in USD) | ||
| required: false | ||
| schema: | ||
| type: string |
There was a problem hiding this comment.
Size prices are number/float, should these filters match that, or stay string with a pattern if the API expects decimals?
There was a problem hiding this comment.
string should be ok here. we're transitioning our price outputs to string as well.
ideally all currencies would be presented as strings.
This PR documents resource filter parameters now available on
GET /v2/sizes