ServicePerimeterEgressPolicy

EgressPolicies match requests based on egressFrom and egressTo stanzas. For an EgressPolicy to match, both egressFrom and egressTo stanzas must be matched. If an EgressPolicy matches a request, the request is allowed to span the ServicePerimeter boundary. For example, an EgressPolicy can be used to allow VMs on networks within the ServicePerimeter to access a defined set of projects outside the perimeter in certain contexts (e.g. to read data from a Cloud Storage bucket or query against a BigQuery dataset). To get more information about ServicePerimeterEgressPolicy, see:

• API documentation

Import

ServicePerimeterEgressPolicy can be imported using any of these accepted formats* {{perimeter}} In Terraform v1.5.0 and later, use an import block to import ServicePerimeterEgressPolicy using one of the formats above. For exampletf import { id = "{{perimeter}}" to = google_access_context_manager_service_perimeter_egress_policy.default }

$ pulumi import gcp:accesscontextmanager/servicePerimeterEgressPolicy:ServicePerimeterEgressPolicy When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), ServicePerimeterEgressPolicy can be imported using one of the formats above. For example

$ pulumi import gcp:accesscontextmanager/servicePerimeterEgressPolicy:ServicePerimeterEgressPolicy default {{perimeter}}