oci.Vault.Secret
Explore with Pulumi AI
This resource provides the Secret resource in Oracle Cloud Infrastructure Vault service.
Creates a new secret according to the details of the request.
Create Secret Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Secret(name: string, args: SecretArgs, opts?: CustomResourceOptions);
@overload
def Secret(resource_name: str,
args: SecretArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Secret(resource_name: str,
opts: Optional[ResourceOptions] = None,
compartment_id: Optional[str] = None,
key_id: Optional[str] = None,
secret_name: Optional[str] = None,
vault_id: Optional[str] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
description: Optional[str] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
metadata: Optional[Mapping[str, Any]] = None,
rotation_config: Optional[_vault.SecretRotationConfigArgs] = None,
secret_content: Optional[_vault.SecretSecretContentArgs] = None,
secret_rules: Optional[Sequence[_vault.SecretSecretRuleArgs]] = None)
func NewSecret(ctx *Context, name string, args SecretArgs, opts ...ResourceOption) (*Secret, error)
public Secret(string name, SecretArgs args, CustomResourceOptions? opts = null)
public Secret(String name, SecretArgs args)
public Secret(String name, SecretArgs args, CustomResourceOptions options)
type: oci:Vault:Secret
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args SecretArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args SecretArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args SecretArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args SecretArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args SecretArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var secretResource = new Oci.Vault.Secret("secretResource", new()
{
CompartmentId = "string",
KeyId = "string",
SecretName = "string",
VaultId = "string",
DefinedTags =
{
{ "string", "any" },
},
Description = "string",
FreeformTags =
{
{ "string", "any" },
},
Metadata =
{
{ "string", "any" },
},
RotationConfig = new Oci.Vault.Inputs.SecretRotationConfigArgs
{
TargetSystemDetails = new Oci.Vault.Inputs.SecretRotationConfigTargetSystemDetailsArgs
{
TargetSystemType = "string",
AdbId = "string",
FunctionId = "string",
},
IsScheduledRotationEnabled = false,
RotationInterval = "string",
},
SecretContent = new Oci.Vault.Inputs.SecretSecretContentArgs
{
ContentType = "string",
Content = "string",
Name = "string",
Stage = "string",
},
SecretRules = new[]
{
new Oci.Vault.Inputs.SecretSecretRuleArgs
{
RuleType = "string",
IsEnforcedOnDeletedSecretVersions = false,
IsSecretContentRetrievalBlockedOnExpiry = false,
SecretVersionExpiryInterval = "string",
TimeOfAbsoluteExpiry = "string",
},
},
});
example, err := Vault.NewSecret(ctx, "secretResource", &Vault.SecretArgs{
CompartmentId: pulumi.String("string"),
KeyId: pulumi.String("string"),
SecretName: pulumi.String("string"),
VaultId: pulumi.String("string"),
DefinedTags: pulumi.Map{
"string": pulumi.Any("any"),
},
Description: pulumi.String("string"),
FreeformTags: pulumi.Map{
"string": pulumi.Any("any"),
},
Metadata: pulumi.Map{
"string": pulumi.Any("any"),
},
RotationConfig: &vault.SecretRotationConfigArgs{
TargetSystemDetails: &vault.SecretRotationConfigTargetSystemDetailsArgs{
TargetSystemType: pulumi.String("string"),
AdbId: pulumi.String("string"),
FunctionId: pulumi.String("string"),
},
IsScheduledRotationEnabled: pulumi.Bool(false),
RotationInterval: pulumi.String("string"),
},
SecretContent: &vault.SecretSecretContentArgs{
ContentType: pulumi.String("string"),
Content: pulumi.String("string"),
Name: pulumi.String("string"),
Stage: pulumi.String("string"),
},
SecretRules: vault.SecretSecretRuleArray{
&vault.SecretSecretRuleArgs{
RuleType: pulumi.String("string"),
IsEnforcedOnDeletedSecretVersions: pulumi.Bool(false),
IsSecretContentRetrievalBlockedOnExpiry: pulumi.Bool(false),
SecretVersionExpiryInterval: pulumi.String("string"),
TimeOfAbsoluteExpiry: pulumi.String("string"),
},
},
})
var secretResource = new Secret("secretResource", SecretArgs.builder()
.compartmentId("string")
.keyId("string")
.secretName("string")
.vaultId("string")
.definedTags(Map.of("string", "any"))
.description("string")
.freeformTags(Map.of("string", "any"))
.metadata(Map.of("string", "any"))
.rotationConfig(SecretRotationConfigArgs.builder()
.targetSystemDetails(SecretRotationConfigTargetSystemDetailsArgs.builder()
.targetSystemType("string")
.adbId("string")
.functionId("string")
.build())
.isScheduledRotationEnabled(false)
.rotationInterval("string")
.build())
.secretContent(SecretSecretContentArgs.builder()
.contentType("string")
.content("string")
.name("string")
.stage("string")
.build())
.secretRules(SecretSecretRuleArgs.builder()
.ruleType("string")
.isEnforcedOnDeletedSecretVersions(false)
.isSecretContentRetrievalBlockedOnExpiry(false)
.secretVersionExpiryInterval("string")
.timeOfAbsoluteExpiry("string")
.build())
.build());
secret_resource = oci.vault.Secret("secretResource",
compartment_id="string",
key_id="string",
secret_name="string",
vault_id="string",
defined_tags={
"string": "any",
},
description="string",
freeform_tags={
"string": "any",
},
metadata={
"string": "any",
},
rotation_config=oci.vault.SecretRotationConfigArgs(
target_system_details=oci.vault.SecretRotationConfigTargetSystemDetailsArgs(
target_system_type="string",
adb_id="string",
function_id="string",
),
is_scheduled_rotation_enabled=False,
rotation_interval="string",
),
secret_content=oci.vault.SecretSecretContentArgs(
content_type="string",
content="string",
name="string",
stage="string",
),
secret_rules=[oci.vault.SecretSecretRuleArgs(
rule_type="string",
is_enforced_on_deleted_secret_versions=False,
is_secret_content_retrieval_blocked_on_expiry=False,
secret_version_expiry_interval="string",
time_of_absolute_expiry="string",
)])
const secretResource = new oci.vault.Secret("secretResource", {
compartmentId: "string",
keyId: "string",
secretName: "string",
vaultId: "string",
definedTags: {
string: "any",
},
description: "string",
freeformTags: {
string: "any",
},
metadata: {
string: "any",
},
rotationConfig: {
targetSystemDetails: {
targetSystemType: "string",
adbId: "string",
functionId: "string",
},
isScheduledRotationEnabled: false,
rotationInterval: "string",
},
secretContent: {
contentType: "string",
content: "string",
name: "string",
stage: "string",
},
secretRules: [{
ruleType: "string",
isEnforcedOnDeletedSecretVersions: false,
isSecretContentRetrievalBlockedOnExpiry: false,
secretVersionExpiryInterval: "string",
timeOfAbsoluteExpiry: "string",
}],
});
type: oci:Vault:Secret
properties:
compartmentId: string
definedTags:
string: any
description: string
freeformTags:
string: any
keyId: string
metadata:
string: any
rotationConfig:
isScheduledRotationEnabled: false
rotationInterval: string
targetSystemDetails:
adbId: string
functionId: string
targetSystemType: string
secretContent:
content: string
contentType: string
name: string
stage: string
secretName: string
secretRules:
- isEnforcedOnDeletedSecretVersions: false
isSecretContentRetrievalBlockedOnExpiry: false
ruleType: string
secretVersionExpiryInterval: string
timeOfAbsoluteExpiry: string
vaultId: string
Secret Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The Secret resource accepts the following input properties:
- Compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- Key
Id string - 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.
- Secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Dictionary<string, object>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- Description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Dictionary<string, object>
- (Updatable) 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:
{"Department": "Finance"}
- Metadata Dictionary<string, object>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- Rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- Secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- Secret
Rules List<SecretSecret Rule> - (Updatable) A list of rules to control how the secret is used and managed.
- Compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- Key
Id string - 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.
- Secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- map[string]interface{}
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- Description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- map[string]interface{}
- (Updatable) 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:
{"Department": "Finance"}
- Metadata map[string]interface{}
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- Rotation
Config SecretRotation Config Args - (Updatable) Defines the frequency of the rotation and the information about the target system
- Secret
Content SecretSecret Content Args - (Updatable) The content of the secret and metadata to help identify it.
- Secret
Rules []SecretSecret Rule Args - (Updatable) A list of rules to control how the secret is used and managed.
- compartment
Id String - (Updatable) The OCID of the compartment where you want to create the secret.
- key
Id String - 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.
- secret
Name String - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- vault
Id String The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Map<String,Object>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description String
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Map<String,Object>
- (Updatable) 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:
{"Department": "Finance"}
- metadata Map<String,Object>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- secret
Rules List<SecretSecret Rule> - (Updatable) A list of rules to control how the secret is used and managed.
- compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- key
Id string - 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.
- secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- {[key: string]: any}
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- {[key: string]: any}
- (Updatable) 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:
{"Department": "Finance"}
- metadata {[key: string]: any}
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- secret
Rules SecretSecret Rule[] - (Updatable) A list of rules to control how the secret is used and managed.
- compartment_
id str - (Updatable) The OCID of the compartment where you want to create the secret.
- key_
id str - 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.
- secret_
name str - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- vault_
id str The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Mapping[str, Any]
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description str
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Mapping[str, Any]
- (Updatable) 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:
{"Department": "Finance"}
- metadata Mapping[str, Any]
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- rotation_
config vault.Secret Rotation Config Args - (Updatable) Defines the frequency of the rotation and the information about the target system
- secret_
content vault.Secret Secret Content Args - (Updatable) The content of the secret and metadata to help identify it.
- secret_
rules Sequence[vault.Secret Secret Rule Args] - (Updatable) A list of rules to control how the secret is used and managed.
- compartment
Id String - (Updatable) The OCID of the compartment where you want to create the secret.
- key
Id String - 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.
- secret
Name String - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- vault
Id String The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Map<Any>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description String
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Map<Any>
- (Updatable) 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:
{"Department": "Finance"}
- metadata Map<Any>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- rotation
Config Property Map - (Updatable) Defines the frequency of the rotation and the information about the target system
- secret
Content Property Map - (Updatable) The content of the secret and metadata to help identify it.
- secret
Rules List<Property Map> - (Updatable) A list of rules to control how the secret is used and managed.
Outputs
All input properties are implicitly available as output properties. Additionally, the Secret resource produces the following output properties:
- Current
Version stringNumber - The version number of the secret version that's currently in use.
- Id string
- The provider-assigned unique ID for this managed resource.
- Last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- Next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Rotation
Status string - Additional information about the status of the secret rotation
- State string
- The current lifecycle state of the secret.
- Time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Current
Version stringNumber - The version number of the secret version that's currently in use.
- Id string
- The provider-assigned unique ID for this managed resource.
- Last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- Next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Rotation
Status string - Additional information about the status of the secret rotation
- State string
- The current lifecycle state of the secret.
- Time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- current
Version StringNumber - The version number of the secret version that's currently in use.
- id String
- The provider-assigned unique ID for this managed resource.
- last
Rotation StringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details String - Additional information about the current lifecycle state of the secret.
- next
Rotation StringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Status String - Additional information about the status of the secret rotation
- state String
- The current lifecycle state of the secret.
- time
Created String - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- current
Version stringNumber - The version number of the secret version that's currently in use.
- id string
- The provider-assigned unique ID for this managed resource.
- last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Status string - Additional information about the status of the secret rotation
- state string
- The current lifecycle state of the secret.
- time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- current_
version_ strnumber - The version number of the secret version that's currently in use.
- id str
- The provider-assigned unique ID for this managed resource.
- last_
rotation_ strtime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle_
details str - Additional information about the current lifecycle state of the secret.
- next_
rotation_ strtime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation_
status str - Additional information about the status of the secret rotation
- state str
- The current lifecycle state of the secret.
- time_
created str - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time_
of_ strcurrent_ version_ expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time_
of_ strdeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- current
Version StringNumber - The version number of the secret version that's currently in use.
- id String
- The provider-assigned unique ID for this managed resource.
- last
Rotation StringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details String - Additional information about the current lifecycle state of the secret.
- next
Rotation StringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Status String - Additional information about the status of the secret rotation
- state String
- The current lifecycle state of the secret.
- time
Created String - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
Look up Existing Secret Resource
Get an existing Secret resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: SecretState, opts?: CustomResourceOptions): Secret
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
compartment_id: Optional[str] = None,
current_version_number: Optional[str] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
description: Optional[str] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
key_id: Optional[str] = None,
last_rotation_time: Optional[str] = None,
lifecycle_details: Optional[str] = None,
metadata: Optional[Mapping[str, Any]] = None,
next_rotation_time: Optional[str] = None,
rotation_config: Optional[_vault.SecretRotationConfigArgs] = None,
rotation_status: Optional[str] = None,
secret_content: Optional[_vault.SecretSecretContentArgs] = None,
secret_name: Optional[str] = None,
secret_rules: Optional[Sequence[_vault.SecretSecretRuleArgs]] = None,
state: Optional[str] = None,
time_created: Optional[str] = None,
time_of_current_version_expiry: Optional[str] = None,
time_of_deletion: Optional[str] = None,
vault_id: Optional[str] = None) -> Secret
func GetSecret(ctx *Context, name string, id IDInput, state *SecretState, opts ...ResourceOption) (*Secret, error)
public static Secret Get(string name, Input<string> id, SecretState? state, CustomResourceOptions? opts = null)
public static Secret get(String name, Output<String> id, SecretState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- Current
Version stringNumber - The version number of the secret version that's currently in use.
- Dictionary<string, object>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- Description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Dictionary<string, object>
- (Updatable) 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:
{"Department": "Finance"}
- Key
Id string - 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.
- Last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- Metadata Dictionary<string, object>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- Next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- Rotation
Status string - Additional information about the status of the secret rotation
- Secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- Secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Secret
Rules List<SecretSecret Rule> - (Updatable) A list of rules to control how the secret is used and managed.
- State string
- The current lifecycle state of the secret.
- Time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- Current
Version stringNumber - The version number of the secret version that's currently in use.
- map[string]interface{}
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- Description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- map[string]interface{}
- (Updatable) 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:
{"Department": "Finance"}
- Key
Id string - 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.
- Last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- Metadata map[string]interface{}
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- Next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Rotation
Config SecretRotation Config Args - (Updatable) Defines the frequency of the rotation and the information about the target system
- Rotation
Status string - Additional information about the status of the secret rotation
- Secret
Content SecretSecret Content Args - (Updatable) The content of the secret and metadata to help identify it.
- Secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Secret
Rules []SecretSecret Rule Args - (Updatable) A list of rules to control how the secret is used and managed.
- State string
- The current lifecycle state of the secret.
- Time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- Vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - (Updatable) The OCID of the compartment where you want to create the secret.
- current
Version StringNumber - The version number of the secret version that's currently in use.
- Map<String,Object>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description String
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Map<String,Object>
- (Updatable) 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:
{"Department": "Finance"}
- key
Id String - 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.
- last
Rotation StringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details String - Additional information about the current lifecycle state of the secret.
- metadata Map<String,Object>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- next
Rotation StringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- rotation
Status String - Additional information about the status of the secret rotation
- secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- secret
Name String - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- secret
Rules List<SecretSecret Rule> - (Updatable) A list of rules to control how the secret is used and managed.
- state String
- The current lifecycle state of the secret.
- time
Created String - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- vault
Id String The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id string - (Updatable) The OCID of the compartment where you want to create the secret.
- current
Version stringNumber - The version number of the secret version that's currently in use.
- {[key: string]: any}
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description string
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- {[key: string]: any}
- (Updatable) 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:
{"Department": "Finance"}
- key
Id string - 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.
- last
Rotation stringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details string - Additional information about the current lifecycle state of the secret.
- metadata {[key: string]: any}
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- next
Rotation stringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Config SecretRotation Config - (Updatable) Defines the frequency of the rotation and the information about the target system
- rotation
Status string - Additional information about the status of the secret rotation
- secret
Content SecretSecret Content - (Updatable) The content of the secret and metadata to help identify it.
- secret
Name string - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- secret
Rules SecretSecret Rule[] - (Updatable) A list of rules to control how the secret is used and managed.
- state string
- The current lifecycle state of the secret.
- time
Created string - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of stringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of stringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- vault
Id string The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment_
id str - (Updatable) The OCID of the compartment where you want to create the secret.
- current_
version_ strnumber - The version number of the secret version that's currently in use.
- Mapping[str, Any]
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description str
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Mapping[str, Any]
- (Updatable) 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:
{"Department": "Finance"}
- key_
id str - 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.
- last_
rotation_ strtime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle_
details str - Additional information about the current lifecycle state of the secret.
- metadata Mapping[str, Any]
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- next_
rotation_ strtime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation_
config vault.Secret Rotation Config Args - (Updatable) Defines the frequency of the rotation and the information about the target system
- rotation_
status str - Additional information about the status of the secret rotation
- secret_
content vault.Secret Secret Content Args - (Updatable) The content of the secret and metadata to help identify it.
- secret_
name str - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- secret_
rules Sequence[vault.Secret Secret Rule Args] - (Updatable) A list of rules to control how the secret is used and managed.
- state str
- The current lifecycle state of the secret.
- time_
created str - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time_
of_ strcurrent_ version_ expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time_
of_ strdeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- vault_
id str The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - (Updatable) The OCID of the compartment where you want to create the secret.
- current
Version StringNumber - The version number of the secret version that's currently in use.
- Map<Any>
- (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"}
- description String
- (Updatable) A brief description of the secret. Avoid entering confidential information.
- Map<Any>
- (Updatable) 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:
{"Department": "Finance"}
- key
Id String - 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.
- last
Rotation StringTime - A property indicating when the secret was last rotated successfully, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- lifecycle
Details String - Additional information about the current lifecycle state of the secret.
- metadata Map<Any>
- (Updatable) Additional metadata that you can use to provide context about how to use the secret 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.
- next
Rotation StringTime - A property indicating when the secret is scheduled to be rotated, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- rotation
Config Property Map - (Updatable) Defines the frequency of the rotation and the information about the target system
- rotation
Status String - Additional information about the status of the secret rotation
- secret
Content Property Map - (Updatable) The content of the secret and metadata to help identify it.
- secret
Name String - A user-friendly name for the secret. Secret names should be unique within a vault. Avoid entering confidential information. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- secret
Rules List<Property Map> - (Updatable) A list of rules to control how the secret is used and managed.
- state String
- The current lifecycle state of the secret.
- time
Created String - A property indicating when the secret was created, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringCurrent Version Expiry - An optional property indicating when the current secret version will expire, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- time
Of StringDeletion - An optional property indicating when to delete the secret, expressed in RFC 3339 timestamp format. Example:
2019-04-03T21:10:29.600Z
- vault
Id String The OCID of the vault where you want to create the secret.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
Supporting Types
SecretRotationConfig, SecretRotationConfigArgs
- Target
System SecretDetails Rotation Config Target System Details - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- Is
Scheduled boolRotation Enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- Rotation
Interval string - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
- Target
System SecretDetails Rotation Config Target System Details - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- Is
Scheduled boolRotation Enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- Rotation
Interval string - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
- target
System SecretDetails Rotation Config Target System Details - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled BooleanRotation Enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval String - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
- target
System SecretDetails Rotation Config Target System Details - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled booleanRotation Enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval string - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
- target_
system_ vault.details Secret Rotation Config Target System Details - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is_
scheduled_ boolrotation_ enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- rotation_
interval str - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
- target
System Property MapDetails - (Updatable) The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled BooleanRotation Enabled - (Updatable) Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval String - (Updatable) The time interval that indicates the frequency for rotating secret data, as described in ISO 8601 format. The minimum value is 1 day and maximum value is 360 days. For example, if you want to set the time interval for rotating a secret data as 30 days, the duration is expressed as "P30D."
SecretRotationConfigTargetSystemDetails, SecretRotationConfigTargetSystemDetailsArgs
- Target
System stringType - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- Adb
Id string - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- Function
Id string - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- Target
System stringType - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- Adb
Id string - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- Function
Id string - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System StringType - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- adb
Id String - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id String - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System stringType - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- adb
Id string - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id string - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target_
system_ strtype - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- adb_
id str - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function_
id str - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System StringType - (Updatable) Unique identifier of the target system that Vault Secret connects to.
- adb
Id String - (Updatable) The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id String - (Updatable) The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
SecretSecretContent, SecretSecretContentArgs
- Content
Type string - (Updatable) The base64-encoded content of the secret.
- Content string
- (Updatable) The base64-encoded content of the secret.
- Name string
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Stage string
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
- Content
Type string - (Updatable) The base64-encoded content of the secret.
- Content string
- (Updatable) The base64-encoded content of the secret.
- Name string
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- Stage string
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
- content
Type String - (Updatable) The base64-encoded content of the secret.
- content String
- (Updatable) The base64-encoded content of the secret.
- name String
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- stage String
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
- content
Type string - (Updatable) The base64-encoded content of the secret.
- content string
- (Updatable) The base64-encoded content of the secret.
- name string
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- stage string
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
- content_
type str - (Updatable) The base64-encoded content of the secret.
- content str
- (Updatable) The base64-encoded content of the secret.
- name str
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- stage str
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
- content
Type String - (Updatable) The base64-encoded content of the secret.
- content String
- (Updatable) The base64-encoded content of the secret.
- name String
- (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
- stage String
- (Updatable) The rotation state of the secret content. The default is
CURRENT
, meaning that the secret is currently in use. A secret version that you mark asPENDING
is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state asPENDING
if you haven't yet updated the secret on the target system. When creating a secret, only the valueCURRENT
is applicable, although the valueLATEST
is also automatically applied. When updating a secret, you can specify a version's rotation state as eitherCURRENT
orPENDING
.
SecretSecretRule, SecretSecretRuleArgs
- Rule
Type string - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- Is
Enforced boolOn Deleted Secret Versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- Is
Secret boolContent Retrieval Blocked On Expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- Secret
Version stringExpiry Interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - Time
Of stringAbsolute Expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
- Rule
Type string - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- Is
Enforced boolOn Deleted Secret Versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- Is
Secret boolContent Retrieval Blocked On Expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- Secret
Version stringExpiry Interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - Time
Of stringAbsolute Expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
- rule
Type String - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- is
Enforced BooleanOn Deleted Secret Versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- is
Secret BooleanContent Retrieval Blocked On Expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- secret
Version StringExpiry Interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - time
Of StringAbsolute Expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
- rule
Type string - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- is
Enforced booleanOn Deleted Secret Versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- is
Secret booleanContent Retrieval Blocked On Expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- secret
Version stringExpiry Interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - time
Of stringAbsolute Expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
- rule_
type str - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- is_
enforced_ boolon_ deleted_ secret_ versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- is_
secret_ boolcontent_ retrieval_ blocked_ on_ expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- secret_
version_ strexpiry_ interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - time_
of_ strabsolute_ expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
- rule
Type String - (Updatable) The type of rule, which either controls when the secret contents expire or whether they can be reused.
- is
Enforced BooleanOn Deleted Secret Versions - (Updatable) A property indicating whether the rule is applied even if the secret version with the content you are trying to reuse was deleted.
- is
Secret BooleanContent Retrieval Blocked On Expiry - (Updatable) A property indicating whether to block retrieval of the secret content, on expiry. The default is false. If the secret has already expired and you would like to retrieve the secret contents, you need to edit the secret rule to disable this property, to allow reading the secret content.
- secret
Version StringExpiry Interval - (Updatable) A property indicating how long the secret contents will be considered valid, expressed in ISO 8601 format. The secret needs to be updated when the secret content expires. The timer resets after you update the secret contents. The minimum value is 1 day and the maximum value is 90 days for this property. Currently, only intervals expressed in days are supported. For example, pass
P3D
to have the secret version expire every 3 days. - time
Of StringAbsolute Expiry - (Updatable) An optional property indicating the absolute time when this secret will expire, expressed in RFC 3339 timestamp format. The minimum number of days from current time is 1 day and the maximum number of days from current time is 365 days. Example:
2019-04-03T21:10:29.600Z
Import
Secrets can be imported using the id
, e.g.
$ pulumi import oci:Vault/secret:Secret test_secret "id"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.