pulumi-aws-kotlin/com.pulumi.aws.networkmanager.kotlin.inputs/GetCoreNetworkPolicyDocumentPlainArgsBuilder/segments

segments

@JvmName(name = "tmbpopqryswttgkb")
suspend fun segments(value: List<GetCoreNetworkPolicyDocumentSegment>)

Parameters

value

Block argument that defines the different segments in the network. Here you can provide descriptions, change defaults, and provide explicit Regional operational and route filters. The names defined for each segment are used in the segment_actions and attachment_policies section. Each segment is created, and operates, as a completely separated routing domain. By default, attachments can only communicate with other attachments in the same segment. Detailed below.

@JvmName(name = "mfnoptrjxlbnbkkq")
suspend fun segments(argument: List<suspend GetCoreNetworkPolicyDocumentSegmentBuilder.() -> Unit>)
@JvmName(name = "hylnetejugkoualx")
suspend fun segments(vararg argument: suspend GetCoreNetworkPolicyDocumentSegmentBuilder.() -> Unit)
@JvmName(name = "iwosftayhiumpknb")
suspend fun segments(argument: suspend GetCoreNetworkPolicyDocumentSegmentBuilder.() -> Unit)

Parameters

argument

Block argument that defines the different segments in the network. Here you can provide descriptions, change defaults, and provide explicit Regional operational and route filters. The names defined for each segment are used in the segment_actions and attachment_policies section. Each segment is created, and operates, as a completely separated routing domain. By default, attachments can only communicate with other attachments in the same segment. Detailed below.

@JvmName(name = "wyybymabkvaluhab")
suspend fun segments(vararg values: GetCoreNetworkPolicyDocumentSegment)

Parameters

values

Block argument that defines the different segments in the network. Here you can provide descriptions, change defaults, and provide explicit Regional operational and route filters. The names defined for each segment are used in the segment_actions and attachment_policies section. Each segment is created, and operates, as a completely separated routing domain. By default, attachments can only communicate with other attachments in the same segment. Detailed below.