Namespace SecretSummary

The OCID of the compartment that contains the secret.

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.

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 secret's current lifecycle state.

The current lifecycle state of the secret.

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 name of the secret.

System tags for this resource. Each key is predefined and scoped to a namespace.

Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}

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 in which the secret exists