The customer tenancy.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
The description of the schedule.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. See Resource Tags. Example: {@code {"bar-key": "value"}}
The OCID representing a unique shedule.
The schedule lifecycle state.
The unique name of the schedule created by the user.
Specifies the supported output file format.
The saved report ID which can also be used to generate a query.
Specifies the frequency according to when the schedule will be run, in the x-obmcs-recurring-time format described in RFC 5545 section 3.3.10. Supported values are : ONE_TIME, DAILY, WEEKLY and MONTHLY.
Usage of system tag keys. These predefined keys are scoped to namespaces. See Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time the schedule was created.
The date and time of the next job execution.
The date and time of the first time job execution.
The schedule.