The OCID of the compartment that contains the work request. Work requests should be scoped to the same compartment as the resource that is affected by the work request. If the work request affects multiple resources, and these resources are not in the same compartment, the service team can choose the primary resource of the compartment to be used.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Simple key-value pair that is applied without any predefined name, type or scope. It exists only for cross-compatibility. Example: {@code {"bar-key": "value"}}
The ID of the work request.
The type of work request.
The percentage of request completed. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The resources affected by this work request.
Status of the current work request.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time when the request was created, as described in RFC 3339, section 14.29.
The date and time when the object was complete, as described in RFC 3339.
The date and time when the request started, as described in RFC 3339, section 14.29.
A summary of the status of a work request.