Autogenerated update (2019-01-26)
Update: - accesscontextmanager_v1beta - appsmarket_v2 - bigquerydatatransfer_v1 - books_v1 - servicenetworking_v1beta - toolresults_v1beta3
This commit is contained in:
1 parent
0b48025248
commit
396ceeb8fa
14 files changed
+142
-61
No files matched your search
@@ -560,8 +560,8 @@ module Google
|
||||
# `ServicePerimeter` to be accessed from the internet. `AccessLevels` listed
|
||||
# must be in the same policy as this `ServicePerimeter`. Referencing a
|
||||
# nonexistent `AccessLevel` is a syntax error. If no `AccessLevel` names are
|
||||
# listed, resources within the perimeter can only be accessed via GCP calls with
|
||||
# request origins within the perimeter. Example:
|
||||
# listed, resources within the perimeter can only be accessed via GCP calls
|
||||
# with request origins within the perimeter. Example:
|
||||
# `"accessPolicies/MY_POLICY/accessLevels/MY_LEVEL"`.
|
||||
# For Service Perimeter Bridge, must be empty.
|
||||
# Corresponds to the JSON property `accessLevels`
|
||||
@@ -592,9 +592,8 @@ module Google
|
||||
# GCP services that are not subject to the Service Perimeter restrictions.
|
||||
# May contain a list of services or a single wildcard "*". For example, if
|
||||
# `logging.googleapis.com` is unrestricted, users can access logs inside the
|
||||
# perimeter as if the perimeter doesn't exist, and it also means VMs inside the
|
||||
# perimeter
|
||||
# can access logs outside the perimeter.
|
||||
# perimeter as if the perimeter doesn't exist, and it also means VMs inside
|
||||
# the perimeter can access logs outside the perimeter.
|
||||
# The wildcard means that unless explicitly specified by
|
||||
# "restricted_services" list, any service is treated as unrestricted. One of
|
||||
# the fields "restricted_services", "unrestricted_services" must contain a
|
||||
|
||||
Reference in new issue
Block a user