Struct google_accesscontextmanager1::api::EgressPolicy
source · pub struct EgressPolicy {
pub egress_from: Option<EgressFrom>,
pub egress_to: Option<EgressTo>,
}
Expand description
Policy for egress from perimeter. EgressPolicies match requests based on egress_from
and egress_to
stanzas. For an EgressPolicy to match, both egress_from
and egress_to
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). EgressPolicies are concerned with the resources that a request relates as well as the API services and API actions being used. They do not related to the direction of data movement. More detailed documentation for this concept can be found in the descriptions of EgressFrom and EgressTo.
This type is not used in any activity, and only used as part of another schema.
Fields§
§egress_from: Option<EgressFrom>
Defines conditions on the source of a request causing this EgressPolicy to apply.
egress_to: Option<EgressTo>
Defines the conditions on the ApiOperation and destination resources that cause this EgressPolicy to apply.
Trait Implementations§
source§impl Clone for EgressPolicy
impl Clone for EgressPolicy
source§fn clone(&self) -> EgressPolicy
fn clone(&self) -> EgressPolicy
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more