The OCID of the compartment where you want to create the secret.
The version number of the secret version that's currently in use. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
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 brief description of the secret. Avoid entering confidential information.
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 secret.
The value of this flag determines whether or not secret content will be generated automatically.
The OCID of the master encryption key that is used to encrypt the secret. You must specify a symmetric key to encrypt the secret during import to the vault. You cannot encrypt secrets with asymmetric keys. Furthermore, the key must exist in the vault that you specify.
A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
Additional information about the current lifecycle state of the secret.
The current lifecycle state of the secret.
Additional metadata that you can use to provide context about how to use the secret or during rotation or other administrative tasks. For example, for a secret that you use to connect to a database, the additional metadata might specify the connection endpoint and the connection string. Provide additional metadata as key-value pairs.
A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
Additional information about the status of the secret rotation
The user-friendly name of the secret. Avoid entering confidential information.
A list of rules that control how the secret is used and managed.
A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example: {@code 2019-04-03T21:10:29.600Z}
The OCID of the vault where the secret exists.
The details of the secret. Secret details do not contain the contents of the secret itself.