-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sagemaker deployment - handle endpoint not found for sagemaker delete #522
sagemaker deployment - handle endpoint not found for sagemaker delete #522
Conversation
Codecov Report
@@ Coverage Diff @@
## master #522 +/- ##
=========================================
Coverage ? 56.41%
=========================================
Files ? 89
Lines ? 6434
Branches ? 0
=========================================
Hits ? 3630
Misses ? 2804
Partials ? 0
Continue to review full report at Codecov.
|
not error_code == 'ValidationException' | ||
or 'Could not find endpoint' not in error_message | ||
): | ||
raise _aws_client_error_to_bentoml_exception(e) | ||
|
||
_try_clean_up_sagemaker_deployment_resource(deployment_pb) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as discussed offline, let's add function delete_sagemaker_endpoint_if_exist
, and call this function in _try_clean_up_sagemaker_deployment_resource
.
rename _try_clean_up_sagemaker_deployment_resource to _delete_sagemaker_deployment_resource_if_exist
…bentoml#522) * handle endpoint not exist for sagemaker delete * include delete endpoint in clean up function * update sagemaker moto
…bentoml#522) * handle endpoint not exist for sagemaker delete * include delete endpoint in clean up function * update sagemaker moto
fix for #504