happygapi.policysimulator.operations — happygapi 0.4.8

Policy Simulator API: operations. Policy Simulator is a collection of endpoints for creating, running, and viewing a Replay. A Replay is a type of simulation that lets you see how your members' access to resources might change if you changed your IAM policy. During a Replay, Policy Simulator re-evaluates, or replays, past access attempts under both the current policy and your proposed policy, and compares those results to determine how your members' access might change under the proposed policy. See: https://cloud.google.com/iam/docs/simulating-accessapi/reference/rest/v1/operations

get$ clj

(get$ auth parameters)

https://cloud.google.com/iam/docs/simulating-accessapi/reference/rest/v1/operations/get

Required parameters: name

Optional parameters: none

Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.

list$ clj

(list$ auth parameters)

https://cloud.google.com/iam/docs/simulating-accessapi/reference/rest/v1/operations/list

Required parameters: none

Optional parameters: name, filter, pageSize, pageToken

Lists operations that match the specified filter in the request. If the server doesn't support this method, it returns UNIMPLEMENTED. NOTE: the name binding allows API services to override the binding to use different resource name schemes, such as users/*/operations. To override the binding, API services can add a binding such as "/v1/{name=users/*}/operations" to their service configuration. For backwards compatibility, the default name includes the operations collection id, however overriding users must ensure the name binding is the parent resource, without the operations collection id.