For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code if-match} parameter to the value of the etag from a previous GET or POST response for that resource. The resource is updated or deleted only if the {@code etag} you provide matches the resource's current {@code etag} value.
The OCID of the model deployment.
Unique Oracle assigned identifier for the request. If you need to contact Oracle about a particular request, then provide the request ID.
RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made
Details for updating a model deployment. Some of the properties of {@code modelDeploymentConfigurationDetails} or {@code CategoryLogDetails} can also be updated with zero down time when the model deployment's lifecycle state is ACTIVE or NEEDS_ATTENTION i.e {@code instanceShapeName}, {@code instanceCount} and {@code modelId}, separately {@code loadBalancerShape} or {@code CategoryLogDetails} can also be updated independently. All of the fields can be updated when the deployment is in the INACTIVE lifecycle state. Changes will take effect the next time the model deployment is activated.
Click here to see how to use UpdateModelDeploymentRequest.