The content type of the secret version's secret contents.
Boolean flag indicating whether secret content for this secret version was auto-generated or not.
The name of the secret version. A name is unique across versions of a secret.
The OCID of the secret.
A list of possible rotation states for the secret version. A secret version marked {@code CURRENT} is currently in use. A secret version marked {@code PENDING} is staged and available for use, but has not been applied on the target system and, therefore, has not been rotated into current, active use. The secret most recently uploaded to a vault is always marked {@code LATEST}. (The first version of a secret is always marked as both {@code CURRENT} and {@code LATEST}.) A secret version marked {@code PREVIOUS} is the secret version that was most recently marked {@code CURRENT}, before the last secret version rotation. A secret version marked {@code DEPRECATED} is neither current, pending, nor the previous one in use. Only secret versions marked {@code DEPRECATED} can be scheduled for deletion.
System tags for this resource. Each key is predefined and scoped to a namespace.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
A optional property indicating when the secret version was created, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
An optional property indicating when to delete the secret version, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
An optional property indicating when the secret version will expire, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
The version number of the secret. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The secret version summary object, which doesn't include the contents of the secret.