google_api_access_context_manager v0.3.0 API Reference
Modules
API calls for all endpoints tagged AccessPolicies
.
API calls for all endpoints tagged Operations
.
Handle Tesla connections for GoogleApi.AccessContextManager.V1.
An AccessLevel
is a label that can be applied to requests to GCP services,
along with a list of requirements necessary for the label to be applied.
AccessPolicy
is a container for AccessLevels
(which define the necessary
attributes to use GCP services) and ServicePerimeters
(which define regions
of services able to freely pass data within a perimeter). An access policy is
globally visible within an organization, and the restrictions it specifies
apply to all projects within an organization.
BasicLevel
is an AccessLevel
using a set of recommended features.
The request message for Operations.CancelOperation.
A condition necessary for an AccessLevel
to be granted. The Condition is an
AND over its fields. So a Condition is true if: 1) the request IP is from one
of the listed subnetworks AND 2) the originating device complies with the
listed device policy AND 3) all listed access levels are granted AND 4) the
request was sent at a time allowed by the DateTimeRestriction.
CustomLevel
is an AccessLevel
using the Cloud Common Expression Language
to represent the necessary conditions for the level to apply to a request.
See CEL spec at: https://github.com/google/cel-spec
DevicePolicy
specifies device specific restrictions necessary to acquire a
given access level. A DevicePolicy
specifies requirements for requests from
devices to be granted access levels, it does not do any enforcement on the
device. DevicePolicy
acts as an AND over all specified fields, and each
repeated field is an OR over its elements. Any unset fields are ignored. For
example, if the proto is { os_type : DESKTOP_WINDOWS, os_type :
DESKTOP_LINUX, encryption_status: ENCRYPTED}, then the DevicePolicy will be
true for requests originating from encrypted Linux desktops and encrypted
Windows desktops.
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance
Represents an expression text. Example
A response to ListAccessLevelsRequest
.
A response to ListAccessPoliciesRequest
.
The response message for Operations.ListOperations.
A response to ListServicePerimetersRequest
.
This resource represents a long-running operation that is the result of a network API call.
A restriction on the OS type and version of devices making requests.
ServicePerimeter
describes a set of GCP 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 GCP
project can only belong to a single regular Service Perimeter. Service
Perimeter Bridges can contain only GCP projects as members, a single GCP
project may belong to multiple Service Perimeter Bridges.
ServicePerimeterConfig
specifies a set of GCP resources that describe
specific Service Perimeter configuration.
The Status
type defines a logical error model that is suitable for
different programming environments, including REST APIs and RPC APIs. It is
used by gRPC. Each Status
message contains
three pieces of data: error code, error message, and error details.