The OCID of the compartment that contains this vault.
The service endpoint to perform cryptographic operations against. Cryptographic operations include Encrypt, Decrypt, and GenerateDataEncryptionKey operations.
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 for the vault. It does not have to be unique, and it is changeable. 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 vault.
A Boolean value that indicates whether the Vault is primary Vault or replica Vault.
The vault's current lifecycle state.
Example: {@code DELETED}
The service endpoint to perform management operations against. Management operations include "Create," "Update," "List," "Get," and "Delete" operations.
The OCID of the vault from which this vault was restored, if it was restored from a backup file. If you restore a vault to the same region, the vault retains the same OCID that it had when you backed up the vault.
The date and time this vault was created, expressed in RFC 3339 timestamp format.
Example: {@code 2018-04-03T21:10:29.600Z}
An optional property to indicate when to delete the vault, expressed in RFC 3339 timestamp format. Example: {@code 2018-04-03T21:10:29.600Z}
The type of vault. Each type of vault stores the key with different degrees of isolation and has different options and pricing.
The OCID of the vault's wrapping key.
The logical entity where the Vault service creates and durably stores keys.