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-04-09 UTC."],[[["The latest version of the `PerimeterType` documentation is 2.5.0, with a history of versions going back to 1.2.0."],["`PerimeterType` has two possible enum values: `Bridge` and `Regular`, describing the two available Perimeter types."],["A regular service perimeter can contain resources, access levels, and restricted services, with each resource only existing in one regular service perimeter."],["Perimeter Bridges can contain resources, but they do not contain access levels or services, and resources can belong to multiple perimeter bridges."],["Perimeter Bridges are useful when multiple perimeters need to share data with a common perimeter but should not share data amongst each other."]]],[]]
