date_expressions
are used to control a resource or cluster option based on the current date/time. They may contain an optional date_spec
and/or duration
object depending on the context.
Table 8.4. Properties of a Date Expression
Field | Description |
---|---|
start
| |
end
|
A date/time conforming to the ISO8601 specification. Can be inferred by supplying a value for
start and a duration .
|
operation
|
Compares the current date/time with the start and/or end date, depending on the context. Allowed values:
|
Note
date_spec
) include the time, the eq
, neq
, gte
and lte
operators have not been implemented since they would only be valid for a single second.
date_spec
objects are used to create cron-like expressions relating to time. Each field can contain a single number or a single range. Instead of defaulting to zero, any field not supplied is ignored.
monthdays="1"
matches the first day of every month and hours="09-17"
matches the hours between 9am and 5pm (inclusive). At this time, multiple ranges (e.g. weekdays="1,2"
or weekdays="1-2,5-6"
) are not supported; depending on demand, this might be implemented in a future release.
Table 8.5. Properties of a Date Specification
Field | Description |
---|---|
id
| |
hours
| |
monthdays
| |
weekdays
| |
yeardays
| |
months
| |
weeks
| |
years
| |
weekyears
| |
moon
|