@윤 도호(Do-Ho Yoon) The cancellation of the delete model operation is not possible if the response code from the delete operation is 204. You can however use the copy model operation to copy the model to a different resource before the delete operation. The steps to perform this are:
- Generate authorization request on the resource to which you will copy the custom model. This operation will provide you the placeholder modelId and access token which will be used in the copy operation.
Output:
{
"modelId": "<model_id>",
"accessToken": "<token>",
"expirationDateTimeTicks": <ticks>
}
- Run the copy model API by passing the following in the body of the request along with the source model id in the request parameter: {
"targetResourceId": "<resource_id_of_the_resource_to_which_the_model_needs_to_be_copied>",
"targetResourceRegion": "<target_resource_region>",
"copyAuthorization": {
"modelId": "<modelid_from_above_operation>",
"accessToken": "<token_from_above_operation>",
"expirationDateTimeTicks": <ticks>
}
}
Output:
Note the result id from the response and check the status in the next step
- Use getCopyModelResult and use the subscription key, result id and source model id from the source resource as the above step.
If the copy is successful you can list the model id from the first step using getCustomModel and see if the copy model is successful.
Please, note that the copy model will work only if the source model is valid i.e the model status should be "ready" to be copied to a different resource.