The availability domain the file system is in. May be unset as a blank or NULL value.
Example: {@code Uocm:PHX-AD-1}
The OCID of the compartment that contains the file system.
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 My file system}
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 OCID of the file system.
Specifies whether the file system has been cloned. See Cloning a File System.
Specifies whether the data has finished copying from the source to the clone. Hydration can take up to several hours to complete depending on the size of the source. The source and clone remain available during hydration, but there may be some performance impact. See Cloning a File System.
The OCID of the KMS key used to encrypt the encryption keys associated with this file system.
Additional information about the current 'lifecycleState'.
The current state of the file system.
The number of bytes consumed by the file system, including any snapshots. This number reflects the metered size of the file system and is updated asynchronously with respect to updates to the file system. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The date and time the file system was created, expressed in RFC 3339 timestamp format.
Example: {@code 2016-08-25T21:10:29.600Z}
Summary information for a file system.