Reference documentation and code samples for the Identity Access Context Manager v1 API enum ServicePerimeter.Types.PerimeterType.
Specifies the type of the Perimeter. There are two types: regular and
bridge. Regular Service Perimeter contains resources, access levels, and
restricted services. Every resource can be in at most ONE
regular Service Perimeter.
In addition to being in a regular service perimeter, a resource can also
be in zero or more perimeter bridges. A perimeter bridge only contains
resources. Cross project operations are permitted if all effected
resources share some perimeter (whether bridge or regular). Perimeter
Bridge does not contain access levels or services: those are governed
entirely by the regular perimeter that resource is in.
Perimeter Bridges are typically useful when building more complex toplogies
with many independent perimeters that need to share some data with a common
perimeter, but should not be able to share data among themselves.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This documentation outlines the `PerimeterType` enum within the Google Identity Access Context Manager v1 API, which is used to specify the type of a service perimeter."],["The latest version of the API available in this document is 2.5.0, and earlier versions back to 1.2.0 are listed with their respective documentation links."],["Two types of service perimeters are defined: `Regular`, which contains resources, access levels, and restricted services, and `Bridge`, which only contains resources and facilitates cross-project operations."],["A resource can belong to at most one regular service perimeter, but can also be a part of multiple perimeter bridges, allowing for flexible and complex network topologies."],["The documentation includes a table showing the `Bridge` and `Regular` fields, along with a short description of each."]]],[]]
