pulumi-gcp-kotlin/com.pulumi.gcp.alloydb.kotlin.inputs/InstancePscInstanceConfigArgs

InstancePscInstanceConfigArgs

data class InstancePscInstanceConfigArgs(val allowedConsumerProjects: Output<List<String>>? = null, val pscDnsName: Output<String>? = null, val pscInterfaceConfigs: Output<List<InstancePscInstanceConfigPscInterfaceConfigArgs>>? = null, val serviceAttachmentLink: Output<String>? = null) : ConvertibleToJava<InstancePscInstanceConfigArgs>

Constructors

Link copied to clipboard
constructor(allowedConsumerProjects: Output<List<String>>? = null, pscDnsName: Output<String>? = null, pscInterfaceConfigs: Output<List<InstancePscInstanceConfigPscInterfaceConfigArgs>>? = null, serviceAttachmentLink: Output<String>? = null)

Properties

Link copied to clipboard
val allowedConsumerProjects: Output<List<String>>? = null

List of consumer projects that are allowed to create PSC endpoints to service-attachments to this instance. These should be specified as project numbers only.

Link copied to clipboard
val pscDnsName: Output<String>? = null

(Output) The DNS name of the instance for PSC connectivity. Name convention: ...alloydb-psc.goog

Link copied to clipboard
val pscInterfaceConfigs: Output<List<InstancePscInstanceConfigPscInterfaceConfigArgs>>? = null

Configurations for setting up PSC interfaces attached to the instance which are used for outbound connectivity. Currently, AlloyDB supports only 0 or 1 PSC interface. Structure is documented below.

Link copied to clipboard
val serviceAttachmentLink: Output<String>? = null

(Output) The service attachment created when Private Service Connect (PSC) is enabled for the instance. The name of the resource will be in the format of projects/<alloydb-tenant-project-number>/regions/<region-name>/serviceAttachments/<service-attachment-name>

Functions

Link copied to clipboard
open override fun toJava(): InstancePscInstanceConfigArgs