com.pulumi.googlenative.accesscontextmanager.v1.inputs.EgressPolicyArgs Maven / Gradle / Ivy
// *** WARNING: this file was generated by pulumi-java-gen. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***
package com.pulumi.googlenative.accesscontextmanager.v1.inputs;
import com.pulumi.core.Output;
import com.pulumi.core.annotations.Import;
import com.pulumi.googlenative.accesscontextmanager.v1.inputs.EgressFromArgs;
import com.pulumi.googlenative.accesscontextmanager.v1.inputs.EgressToArgs;
import java.util.Objects;
import java.util.Optional;
import javax.annotation.Nullable;
/**
* 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.
*
*/
public final class EgressPolicyArgs extends com.pulumi.resources.ResourceArgs {
public static final EgressPolicyArgs Empty = new EgressPolicyArgs();
/**
* Defines conditions on the source of a request causing this EgressPolicy to apply.
*
*/
@Import(name="egressFrom")
private @Nullable Output egressFrom;
/**
* @return Defines conditions on the source of a request causing this EgressPolicy to apply.
*
*/
public Optional
© 2015 - 2024 Weber Informatics LLC | Privacy Policy