The availability domain that the file system snapshot policy is in.
Example: {@code Uocm:PHX-AD-1}
The OCID of the compartment that contains the file system snapshot policy.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A user-friendly name. It does not have to be unique, and it is changeable. Avoid entering confidential information.
Example: {@code policy1}
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}
The prefix to apply to all snapshots created by this policy.
Example: {@code acme}
The list of associated snapshot schedules. A maximum of 10 schedules can be associated with a policy.
If using the CLI, provide the schedule as a list of JSON strings, with the list wrapped in quotation marks, i.e. {@code --schedules '[{\"timeZone\":\"UTC\",\"period\":\"DAILY\",\"hourOfDay\":18},{\"timeZone\":\"UTC\",\"period\":\"HOURLY\"}]' }
Details for creating the file system snapshot policy.