pulumi-gcp-kotlin/com.pulumi.gcp.alloydb.kotlin.outputs/InstancePscInstanceConfig

InstancePscInstanceConfig

data class InstancePscInstanceConfig(val allowedConsumerProjects: List<String>? = null, val pscDnsName: String? = null, val pscInterfaceConfigs: List<InstancePscInstanceConfigPscInterfaceConfig>? = null, val serviceAttachmentLink: String? = null)

Constructors

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

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard
val allowedConsumerProjects: 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: String? = null

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

Link copied to clipboard
val pscInterfaceConfigs: List<InstancePscInstanceConfigPscInterfaceConfig>? = 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: 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>