Permissions Required for Each API Operation

This table below lists the Resource Scheduler API operations in a logical order, grouped by resource type.

For information about permissions, see Permissions.
Note

Operation Specific Attributes. List the operation specific attributes that you will make available to the policy compiler, as shown here.

For a specific resource kind, you must have the same set of attributes across all operations (get, list, delete, and more). The one exception is for the Create operation, where you do not have the ID for that object yet, so you can't have a target.RESOURCE-KIND.id attribute for Create.

API Permissions Required to Use the Operation Operation
ListSchedules RESOURCE_SCHEDULE_INSPECT Return a list of resource schedules.
GetSchedule RESOURCE_SCHEDULE_READ Get a resource schedule.
CreateSchedule RESOURCE_SCHEDULE_CREATE Create a resource schedule.
UpdateSchedule RESOURCE_SCHEDULE_UPDATE Update a resource schedule.
DeleteSchedule RESOURCE_SCHEDULE_DELETE Delete a resource schedule.
ChangeScheduleCompartment RESOURCE_SCHEDULE_MOVE Change resource schedule compartment
ListWorkRequests RESOURCE_SCHEDULE_

WORKREQUEST_INSPECT

List work requests associated with a resource schedule.
GetWorkRequest RESOURCE_SCHEDULE_

WORKREQUEST_READ

Get a work request.

Metaverb Map

Resource type Inspect Read Use Manage
RESOURCE-SCHEDULE RESOURCE_

SCHEDULE

_INSPECT
RESOURCE_

SCHEDULE

_READ
N/A

RESOURCE_SCHEDULE_CREATE RESOURCE_SCHEDULE_UPDATE RESOURCE_SCHEDULE_UPDATE RESOURCE_SCHEDULE_MOVE RESOURCE_SCHEDULE_DELETE

RESOURCE-SCHEDULE-WORKREQUEST RESOURCE_

SCHEDULE_

WORKREQUEST_

INSPECT

RESOURCE_

SCHEDULE_

WORKREQUEST_

READ

N/A N/A

Was this article helpful?