Conversation
mojojoji
left a comment
There was a problem hiding this comment.
Added some comments but we can merge this and tackle those in upcoming PRs
src/together/cli/api/endpoints.py
Outdated
There was a problem hiding this comment.
This does not instantly stop the endpoint. It moves to STOPPING state and then after some time STOPPED. We can change the message here to indicate that STOPPING is initiated. Maybe we can also add a --wait option to wait for the STOPPED state.
src/together/cli/api/endpoints.py
Outdated
There was a problem hiding this comment.
Same as stoppped. In start it moves to PENDING and the STARTING and then STARTED. So we can change the message and maybe add a --wait option
src/together/resources/endpoints.py
Outdated
There was a problem hiding this comment.
This check is not needed as the api supports updating just one of min or max replicas. There is no harm in doing a check here but then we can avoid the get call.
There was a problem hiding this comment.
I think we need to update the OpenAPI spec in that case, because the autoscaling object currently says min_replicas and max_replicas are required. So that's not the case?
|
YAY! The tests pass! Ultimately I had to include the generated OpenAPI client files in the repo, because whatever I tried, Poetry (or pip) would not include them. I tried |
8a8f537 to
e68aa19
Compare
Have you read the Contributing Guidelines?
Describe your changes
Adds the ability to create, stop, delete start, list and update dedicated endpoints from the CLI:
This approach is a bit different than the other resources. In this case, I have generated an OpenAPI client from our public OpenAPI spec, and used that within the CLI (and resource) to call everything inside dedicated. Because of this, I have added amakejob to also generate the client, and I have updated the spec (here: togethercomputer/openapi#64). We'll need to merge both PRs for dedicated endpoint support.