ServicePerimeter
import type { ServicePerimeter } from "https://googleapis.deno.dev/v1/accesscontextmanager:v1.ts";
ServicePerimeter
describes a set of Google Cloud resources which can
freely import and export data amongst themselves, but not export outside of
the ServicePerimeter
. If a request with a source within this
ServicePerimeter
has a target outside of the ServicePerimeter
, the
request will be blocked. Otherwise the request is allowed. There are two
types of Service Perimeter - Regular and Bridge. Regular Service Perimeters
cannot overlap, a single Google Cloud project or VPC network can only belong
to a single regular Service Perimeter. Service Perimeter Bridges can contain
only Google Cloud projects as members, a single Google Cloud project may
belong to multiple Service Perimeter Bridges.
§Properties
Description of the ServicePerimeter
and its use. Does not affect
behavior.
Resource name for the ServicePerimeter
. Format:
accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}
. The
service_perimeter
component must begin with a letter, followed by
alphanumeric characters or _
. After you create a ServicePerimeter
, you
cannot change its name
.
Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the "use_explicit_dry_run_spec" flag is set.
Current ServicePerimeter configuration. Specifies sets of resources, restricted services and access levels that determine perimeter content and boundaries.
Use explicit dry run spec flag. Ordinarily, a dry-run spec implicitly exists for all Service Perimeters, and that spec is identical to the status for those Service Perimeters. When this flag is set, it inhibits the generation of the implicit spec, thereby allowing the user to explicitly provide a configuration ("spec") to use in a dry-run version of the Service Perimeter. This allows the user to test changes to the enforced config ("status") without actually enforcing them. This testing is done through analyzing the differences between currently enforced and suggested restrictions. use_explicit_dry_run_spec must bet set to True if any of the fields in the spec are set to non-default values.