happygapi.accesscontextmanager.accessPolicies — happygapi 0.4.7

Access Context Manager API: accessPolicies. An API for setting attribute based access control to requests to GCP services. See: https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies

accessLevels-create$ clj

(accessLevels-create$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/create

Required parameters: parent

Optional parameters: none

Body:

{:basic {:conditions [Condition], :combiningFunction string}, :description string, :name string, :custom {:expr Expr}, :title string}

Create an Access Level. The longrunning operation from this RPC will have a successful status once the Access Level has propagated to long-lasting storage. Access Levels containing errors will result in an error response for the first error encountered.

accessLevels-delete$ clj

(accessLevels-delete$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/delete

Required parameters: name

Optional parameters: none

Delete an Access Level by resource name. The longrunning operation from this RPC will have a successful status once the Access Level has been removed from long-lasting storage.

accessLevels-get$ clj

(accessLevels-get$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/get

Required parameters: name

Optional parameters: accessLevelFormat

Get an Access Level by resource name.

accessLevels-list$ clj

(accessLevels-list$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/list

Required parameters: parent

Optional parameters: pageSize, accessLevelFormat, pageToken

List all Access Levels for an access policy.

accessLevels-patch$ clj

(accessLevels-patch$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/patch

Required parameters: name

Optional parameters: updateMask

Body:

{:basic {:conditions [Condition], :combiningFunction string}, :description string, :name string, :custom {:expr Expr}, :title string}

Update an Access Level. The longrunning operation from this RPC will have a successful status once the changes to the Access Level have propagated to long-lasting storage. Access Levels containing errors will result in an error response for the first error encountered.

accessLevels-replaceAll$ clj

(accessLevels-replaceAll$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/accessLevels/replaceAll

Required parameters: parent

Optional parameters: none

Body:

{:accessLevels [{:basic BasicLevel, :description string, :name string, :custom CustomLevel, :title string}], :etag string}

Replace all existing Access Levels in an Access Policy with the Access Levels provided. This is done atomically. The longrunning operation from this RPC will have a successful status once all replacements have propagated to long-lasting storage. Replacements containing errors will result in an error response for the first error encountered. Replacement will be cancelled on error, existing Access Levels will not be affected. Operation.response field will contain ReplaceAccessLevelsResponse. Removing Access Levels contained in existing Service Perimeters will result in error.

create$ clj

(create$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/create

Required parameters: none

Optional parameters: none

Body:

{:name string, :etag string, :parent string, :title string}

Create an AccessPolicy. Fails if this organization already has a AccessPolicy. The longrunning Operation will have a successful status once the AccessPolicy has propagated to long-lasting storage. Syntactic and basic semantic errors will be returned in metadata as a BadRequest proto.

delete$ clj

(delete$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/delete

Required parameters: name

Optional parameters: none

Delete an AccessPolicy by resource name. The longrunning Operation will have a successful status once the AccessPolicy has been removed from long-lasting storage.

get$ clj

(get$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/get

Required parameters: name

Optional parameters: none

Get an AccessPolicy by name.

list$ clj

(list$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/list

Required parameters: none

Optional parameters: pageToken, pageSize, parent

List all AccessPolicies under a container.

patch$ clj

(patch$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/patch

Required parameters: name

Optional parameters: updateMask

Body:

{:name string, :etag string, :parent string, :title string}

Update an AccessPolicy. The longrunning Operation from this RPC will have a successful status once the changes to the AccessPolicy have propagated to long-lasting storage. Syntactic and basic semantic errors will be returned in metadata as a BadRequest proto.

servicePerimeters-commit$ clj

(servicePerimeters-commit$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/commit

Required parameters: parent

Optional parameters: none

Body:

{:etag string}

Commit the dry-run spec for all the Service Perimeters in an Access Policy. A commit operation on a Service Perimeter involves copying its spec field to that Service Perimeter's status field. Only Service Perimeters with use_explicit_dry_run_spec field set to true are affected by a commit operation. The longrunning operation from this RPC will have a successful status once the dry-run specs for all the Service Perimeters have been committed. If a commit fails, it will cause the longrunning operation to return an error response and the entire commit operation will be cancelled. When successful, Operation.response field will contain CommitServicePerimetersResponse. The dry_run and the spec fields will be cleared after a successful commit operation.

servicePerimeters-create$ clj

(servicePerimeters-create$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/create

Required parameters: parent

Optional parameters: none

Body:

{:title string, :spec {:vpcAccessibleServices VpcAccessibleServices, :accessLevels [string], :resources [string], :egressPolicies [EgressPolicy], :restrictedServices [string], :ingressPolicies [IngressPolicy]}, :useExplicitDryRunSpec boolean, :status {:vpcAccessibleServices VpcAccessibleServices, :accessLevels [string], :resources [string], :egressPolicies [EgressPolicy], :restrictedServices [string], :ingressPolicies [IngressPolicy]}, :description string, :name string, :perimeterType string}

Create a Service Perimeter. The longrunning operation from this RPC will have a successful status once the Service Perimeter has propagated to long-lasting storage. Service Perimeters containing errors will result in an error response for the first error encountered.

servicePerimeters-delete$ clj

(servicePerimeters-delete$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/delete

Required parameters: name

Optional parameters: none

Delete a Service Perimeter by resource name. The longrunning operation from this RPC will have a successful status once the Service Perimeter has been removed from long-lasting storage.

servicePerimeters-get$ clj

(servicePerimeters-get$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/get

Required parameters: name

Optional parameters: none

Get a Service Perimeter by resource name.

servicePerimeters-list$ clj

(servicePerimeters-list$ auth parameters)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/list

Required parameters: parent

Optional parameters: pageSize, pageToken

List all Service Perimeters for an access policy.

servicePerimeters-patch$ clj

(servicePerimeters-patch$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/patch

Required parameters: name

Optional parameters: updateMask

Body:

{:title string, :spec {:vpcAccessibleServices VpcAccessibleServices, :accessLevels [string], :resources [string], :egressPolicies [EgressPolicy], :restrictedServices [string], :ingressPolicies [IngressPolicy]}, :useExplicitDryRunSpec boolean, :status {:vpcAccessibleServices VpcAccessibleServices, :accessLevels [string], :resources [string], :egressPolicies [EgressPolicy], :restrictedServices [string], :ingressPolicies [IngressPolicy]}, :description string, :name string, :perimeterType string}

Update a Service Perimeter. The longrunning operation from this RPC will have a successful status once the changes to the Service Perimeter have propagated to long-lasting storage. Service Perimeter containing errors will result in an error response for the first error encountered.

servicePerimeters-replaceAll$ clj

(servicePerimeters-replaceAll$ auth parameters body)

https://cloud.google.com/access-context-manager/docs/reference/rest/api/reference/rest/v1/accessPolicies/servicePerimeters/replaceAll

Required parameters: parent

Optional parameters: none

Body:

{:etag string, :servicePerimeters [{:title string, :spec ServicePerimeterConfig, :useExplicitDryRunSpec boolean, :status ServicePerimeterConfig, :description string, :name string, :perimeterType string}]}

Replace all existing Service Perimeters in an Access Policy with the Service Perimeters provided. This is done atomically. The longrunning operation from this RPC will have a successful status once all replacements have propagated to long-lasting storage. Replacements containing errors will result in an error response for the first error encountered. Replacement will be cancelled on error, existing Service Perimeters will not be affected. Operation.response field will contain ReplaceServicePerimetersResponse.