Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi
oci.Vault.getSecret
Explore with Pulumi AI
Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi
This data source provides details about a specific Secret resource in Oracle Cloud Infrastructure Vault service.
Gets information about the specified secret.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testSecret = oci.Vault.getSecret({
secretId: testSecretOciVaultSecret.id,
});
import pulumi
import pulumi_oci as oci
test_secret = oci.Vault.get_secret(secret_id=test_secret_oci_vault_secret["id"])
package main
import (
"github.com/pulumi/pulumi-oci/sdk/go/oci/Vault"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := Vault.GetSecret(ctx, &vault.GetSecretArgs{
SecretId: testSecretOciVaultSecret.Id,
}, nil)
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testSecret = Oci.Vault.GetSecret.Invoke(new()
{
SecretId = testSecretOciVaultSecret.Id,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Vault.VaultFunctions;
import com.pulumi.oci.Vault.inputs.GetSecretArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var testSecret = VaultFunctions.getSecret(GetSecretArgs.builder()
.secretId(testSecretOciVaultSecret.id())
.build());
}
}
variables:
testSecret:
fn::invoke:
Function: oci:Vault:getSecret
Arguments:
secretId: ${testSecretOciVaultSecret.id}
Using getSecret
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getSecret(args: GetSecretArgs, opts?: InvokeOptions): Promise<GetSecretResult>
function getSecretOutput(args: GetSecretOutputArgs, opts?: InvokeOptions): Output<GetSecretResult>
def get_secret(secret_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetSecretResult
def get_secret_output(secret_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetSecretResult]
func GetSecret(ctx *Context, args *GetSecretArgs, opts ...InvokeOption) (*GetSecretResult, error)
func GetSecretOutput(ctx *Context, args *GetSecretOutputArgs, opts ...InvokeOption) GetSecretResultOutput
> Note: This function is named GetSecret
in the Go SDK.
public static class GetSecret
{
public static Task<GetSecretResult> InvokeAsync(GetSecretArgs args, InvokeOptions? opts = null)
public static Output<GetSecretResult> Invoke(GetSecretInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetSecretResult> getSecret(GetSecretArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Vault/getSecret:getSecret
arguments:
# arguments dictionary
The following arguments are supported:
- Secret
Id string - The OCID of the secret.
- Secret
Id string - The OCID of the secret.
- secret
Id String - The OCID of the secret.
- secret
Id string - The OCID of the secret.
- secret_
id str - The OCID of the secret.
- secret
Id String - The OCID of the secret.
getSecret Result
The following output properties are available:
- Compartment
Id string - 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>
- 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
- A brief description of the secret. Avoid entering confidential information.
- Dictionary<string, object>
- 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"}
- Id string
- The OCID of 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.
- 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>
- 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.
- 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
Configs List<GetSecret Rotation Config> - 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
Contents List<GetSecret Secret Content> - Secret
Id string - Secret
Name string - The user-friendly name of the secret. Avoid entering confidential information.
- Secret
Rules List<GetSecret Secret Rule> - A list of rules that 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 in which the secret exists
- Compartment
Id string - 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{}
- 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
- A brief description of the secret. Avoid entering confidential information.
- map[string]interface{}
- 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"}
- Id string
- The OCID of 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.
- 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{}
- 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.
- 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
Configs []GetSecret Rotation Config - 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
Contents []GetSecret Secret Content - Secret
Id string - Secret
Name string - The user-friendly name of the secret. Avoid entering confidential information.
- Secret
Rules []GetSecret Secret Rule - A list of rules that 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 in which the secret exists
- compartment
Id String - 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>
- 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
- A brief description of the secret. Avoid entering confidential information.
- Map<String,Object>
- 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"}
- id String
- The OCID of 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.
- 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>
- 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.
- 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
Configs List<GetSecret Rotation Config> - 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
Contents List<GetSecret Secret Content> - secret
Id String - secret
Name String - The user-friendly name of the secret. Avoid entering confidential information.
- secret
Rules List<GetSecret Secret Rule> - A list of rules that 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 in which the secret exists
- compartment
Id string - 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}
- 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
- A brief description of the secret. Avoid entering confidential information.
- {[key: string]: any}
- 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"}
- id string
- The OCID of 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.
- 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}
- 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.
- 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
Configs GetSecret Rotation Config[] - 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
Contents GetSecret Secret Content[] - secret
Id string - secret
Name string - The user-friendly name of the secret. Avoid entering confidential information.
- secret
Rules GetSecret Secret Rule[] - A list of rules that 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 in which the secret exists
- compartment_
id str - 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]
- 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
- A brief description of the secret. Avoid entering confidential information.
- Mapping[str, Any]
- 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"}
- id str
- The OCID of 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.
- 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]
- 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.
- 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_
configs Sequence[vault.Get Secret Rotation Config] - 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_
contents Sequence[vault.Get Secret Secret Content] - secret_
id str - secret_
name str - The user-friendly name of the secret. Avoid entering confidential information.
- secret_
rules Sequence[vault.Get Secret Secret Rule] - A list of rules that 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 in which the secret exists
- compartment
Id String - 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>
- 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
- A brief description of the secret. Avoid entering confidential information.
- Map<Any>
- 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"}
- id String
- The OCID of 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.
- 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>
- 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.
- 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
Configs List<Property Map> - 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
Contents List<Property Map> - secret
Id String - secret
Name String - The user-friendly name of the secret. Avoid entering confidential information.
- secret
Rules List<Property Map> - A list of rules that 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 in which the secret exists
Supporting Types
GetSecretRotationConfig
- Is
Scheduled boolRotation Enabled - Enables auto rotation, when set to true rotationInterval must be set.
- Rotation
Interval string - 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 List<GetDetails Secret Rotation Config Target System Detail> - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- Is
Scheduled boolRotation Enabled - Enables auto rotation, when set to true rotationInterval must be set.
- Rotation
Interval string - 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 []GetDetails Secret Rotation Config Target System Detail - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled BooleanRotation Enabled - Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval String - 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 List<GetDetails Secret Rotation Config Target System Detail> - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled booleanRotation Enabled - Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval string - 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 GetDetails Secret Rotation Config Target System Detail[] - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is_
scheduled_ boolrotation_ enabled - Enables auto rotation, when set to true rotationInterval must be set.
- rotation_
interval str - 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_ Sequence[vault.details Get Secret Rotation Config Target System Detail] - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
- is
Scheduled BooleanRotation Enabled - Enables auto rotation, when set to true rotationInterval must be set.
- rotation
Interval String - 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 List<Property Map>Details - The TargetSystemDetails provides the targetSystem type and type-specific connection metadata
GetSecretRotationConfigTargetSystemDetail
- Adb
Id string - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- Function
Id string - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- Target
System stringType - Unique identifier of the target system that Vault Secret connects to.
- Adb
Id string - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- Function
Id string - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- Target
System stringType - Unique identifier of the target system that Vault Secret connects to.
- adb
Id String - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id String - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System StringType - Unique identifier of the target system that Vault Secret connects to.
- adb
Id string - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id string - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System stringType - Unique identifier of the target system that Vault Secret connects to.
- adb_
id str - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function_
id str - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target_
system_ strtype - Unique identifier of the target system that Vault Secret connects to.
- adb
Id String - The unique identifier (OCID) for the autonomous database that Vault Secret connects to.
- function
Id String - The unique identifier (OCID) of the Oracle Cloud Infrastructure Functions that vault secret connects to.
- target
System StringType - Unique identifier of the target system that Vault Secret connects to.
GetSecretSecretContent
- Content string
- Content
Type string - Name string
- Stage string
- Content string
- Content
Type string - Name string
- Stage string
- content String
- content
Type String - name String
- stage String
- content string
- content
Type string - name string
- stage string
- content str
- content_
type str - name str
- stage str
- content String
- content
Type String - name String
- stage String
GetSecretSecretRule
- Is
Enforced boolOn Deleted Secret Versions - 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 - 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.
- Rule
Type string - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- Secret
Version stringExpiry Interval - 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 - 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
- Is
Enforced boolOn Deleted Secret Versions - 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 - 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.
- Rule
Type string - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- Secret
Version stringExpiry Interval - 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 - 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
- is
Enforced BooleanOn Deleted Secret Versions - 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 - 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.
- rule
Type String - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- secret
Version StringExpiry Interval - 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 - 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
- is
Enforced booleanOn Deleted Secret Versions - 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 - 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.
- rule
Type string - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- secret
Version stringExpiry Interval - 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 - 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
- is_
enforced_ boolon_ deleted_ secret_ versions - 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 - 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.
- rule_
type str - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- secret_
version_ strexpiry_ interval - 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 - 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
- is
Enforced BooleanOn Deleted Secret Versions - 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 - 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.
- rule
Type String - The type of rule, which either controls when the secret contents expire or whether they can be reused.
- secret
Version StringExpiry Interval - 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 - 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
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.
Oracle Cloud Infrastructure v1.41.0 published on Wednesday, Jun 19, 2024 by Pulumi