Update the deployment metadata. The following parameters of deployment metadata are supported for the patch operation.

/tags - /name - /description - /custom - /hardware_spec - /hybrid_pipeline_hardware_specs - /asset - /online/parameters In case of online deployments, using PATCH operation of /ml/v4/deployments, users can update the number of copies of an online deployment. Users can specify the desired value of number of copies in hardware_spec.num_nodes parameter. As hardware_spec.name or hardware_spec.id is mandatory for hardware_spec schema, a valid value such as XS, S must be specified for hardware_spec.name parameter as part of PATCH request. Alternatively, users can also specify a valid ID of a hardware specification in hardware_spec.id parameter. However, changes related to hardware_spec.name or hardware_spec.id specified in PATCH operation will not be applied for online deployments.
In case of batch deployments, using PATCH operation of /ml/v4/deployments, users can update the hardware specification so that subsequent batch deployment jobs can make use of the updated compute configurations. To update the compute configuration, users must specify a valid value for either hardware_spec.name or hardware_spec.id of the hardware specification that suits their requirement. In the batch deployment context, hardware_spec.num_nodes parameter is not currently supported.
When 'asset' is patched with id/rev:
Deployment with the patched id/rev is started. - With an asynchronous deployment (version greater than 2021-05-01), 202 response code will be returned and one can poll the deployment for the status.
If any failures, deployment will be reverted back to the previous id/rev and the failure message will be captured in 'failures' field in the response.

In the case of an online deployment, the PATCH operation with path specified as /online/parameters can be used to update the serving_name.