Service Mesh Work Requests
Service Mesh work requests allow you to monitor long-running operations such as the mesh or virtual service creation. When you launch an operation, the Service Mesh spawns a work request. A work request is an activity log that enables you to track each step in the operation's progress. Each work request has an OCID that allows you to interact with it programmatically and use it for automation.
Work Request Status
Many Service Mesh requests don't take effect immediately. The request spawns an asynchronous workflow for fulfillment. Some operations depend on the completion of a preceding operation before completing. You can monitor each operation’s work request and confirm that the operation succeeds before proceeding to the next operation.
For example, if you want to create a virtual service and add it to a service mesh, you first must create the service mesh. Service Mesh creates the virtual service only after the operation completes.
For a detailed list of status values and what they mean, see: Work Requests.
Work Request Operations
You can perform the following work request operations.