Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace WorkRequest

Many of the API requests you use to create and configure load balancing do not take effect immediately. In these cases, the request spawns an asynchronous work flow to fulfill the request. WorkRequest objects provide visibility for in-progress work flows. For more information about work requests, see Viewing the State of a Work Request.

Properties

Optional compartmentId

compartmentId: undefined | string

The OCID of the compartment containing the load balancer.

errorDetails

errorDetails: Array<WorkRequestError>

id

id: string

The OCID of the work request.

lifecycleState

lifecycleState: LifecycleState

The current state of the work request.

loadBalancerId

loadBalancerId: string

The OCID of the load balancer with which the work request is associated.

message

message: string

A collection of data, related to the load balancer provisioning process, that helps with debugging in the event of failure. Possible data elements include:

- workflow name - event ID - work request ID - load balancer ID - workflow completion message

timeAccepted

timeAccepted: Date

The date and time the work request was created, in the format defined by RFC3339.

Example: {@code 2016-08-25T21:10:29.600Z}

Optional timeFinished

timeFinished: Date

The date and time the work request was completed, in the format defined by RFC3339.

Example: {@code 2016-08-25T21:10:29.600Z}

type

type: string

The type of action the work request represents.

Example: {@code CreateListener}

Functions

getDeserializedJsonObj

getJsonObj