You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What
Ability (new command or probably better an update option on the existing deploy command) to update an endpoint’s configuration. As of today, if we deploy an endpoint there’s no way of amending its configuration e.g. instance type.
Running deploy using different params and the same endpoint name does not work unfortunately, SageMaker throws a duplicate endpoint exception.
The text was updated successfully, but these errors were encountered:
Essentially, I'll add a new flag argument --overwrite that will require the --endpoint-name to be compulsory as we need to know which endpoint to update. What are your thoughts?
Looks good @pm3310 . The only alternative I can think of at the moment is implicitly updating if the endpoint name already exists.
That is, if endoint-name is provided, check if an endpoint with that name exists; yes -> call SageMaker’s update config API(s), no -> create new endpoint.
This has the advantage of no new options being added and less work (I think) needed both for the PR and end users.
If I’m right, we would only need to make changes here and the docs.
What
Ability (new command or probably better an update option on the existing deploy command) to update an endpoint’s configuration. As of today, if we deploy an endpoint there’s no way of amending its configuration e.g. instance type.
Running
deploy
using different params and the same endpoint name does not work unfortunately, SageMaker throws a duplicate endpoint exception.The text was updated successfully, but these errors were encountered: