Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GoogleCloudPolicytroubleshooterIamV3AllowBindingExplanation

import type { GoogleCloudPolicytroubleshooterIamV3AllowBindingExplanation } from "https://googleapis.deno.dev/v1/policytroubleshooter:v3.ts";

Details about how a role binding in an allow policy affects a principal's ability to use a permission.

interface GoogleCloudPolicytroubleshooterIamV3AllowBindingExplanation {
allowAccessState?:
| "ALLOW_ACCESS_STATE_UNSPECIFIED"
| "ALLOW_ACCESS_STATE_GRANTED"
| "ALLOW_ACCESS_STATE_NOT_GRANTED"
| "ALLOW_ACCESS_STATE_UNKNOWN_CONDITIONAL"
| "ALLOW_ACCESS_STATE_UNKNOWN_INFO";
condition?: GoogleTypeExpr;
relevance?: "HEURISTIC_RELEVANCE_UNSPECIFIED" | "HEURISTIC_RELEVANCE_NORMAL" | "HEURISTIC_RELEVANCE_HIGH";
role?: string;
rolePermission?:
| "ROLE_PERMISSION_INCLUSION_STATE_UNSPECIFIED"
| "ROLE_PERMISSION_INCLUDED"
| "ROLE_PERMISSION_NOT_INCLUDED"
| "ROLE_PERMISSION_UNKNOWN_INFO";
rolePermissionRelevance?: "HEURISTIC_RELEVANCE_UNSPECIFIED" | "HEURISTIC_RELEVANCE_NORMAL" | "HEURISTIC_RELEVANCE_HIGH";
}

§Properties

§
allowAccessState?: "ALLOW_ACCESS_STATE_UNSPECIFIED" | "ALLOW_ACCESS_STATE_GRANTED" | "ALLOW_ACCESS_STATE_NOT_GRANTED" | "ALLOW_ACCESS_STATE_UNKNOWN_CONDITIONAL" | "ALLOW_ACCESS_STATE_UNKNOWN_INFO"
[src]

Required. Indicates whether this role binding gives the specified permission to the specified principal on the specified resource. This field does not indicate whether the principal actually has the permission on the resource. There might be another role binding that overrides this role binding. To determine whether the principal actually has the permission, use the overall_access_state field in the TroubleshootIamPolicyResponse.

§

The combined result of all memberships. Indicates if the principal is included in any role binding, either directly or indirectly.

§

A condition expression that specifies when the role binding grants access. To learn about IAM Conditions, see https://cloud.google.com/iam/help/conditions/overview.

§

Condition evaluation state for this role binding.

§

Indicates whether each role binding includes the principal specified in the request, either directly or indirectly. Each key identifies a principal in the role binding, and each value indicates whether the principal in the role binding includes the principal in the request. For example, suppose that a role binding includes the following principals: * user:alice@example.com * group:product-eng@example.com You want to troubleshoot access for user:bob@example.com. This user is a member of the group group:product-eng@example.com. For the first principal in the role binding, the key is user:alice@example.com, and the membership field in the value is set to NOT_INCLUDED. For the second principal in the role binding, the key is group:product-eng@example.com, and the membership field in the value is set to INCLUDED.

§
relevance?: "HEURISTIC_RELEVANCE_UNSPECIFIED" | "HEURISTIC_RELEVANCE_NORMAL" | "HEURISTIC_RELEVANCE_HIGH"
[src]

The relevance of this role binding to the overall determination for the entire policy.

§
role?: string
[src]

The role that this role binding grants. For example, roles/compute.admin. For a complete list of predefined IAM roles, as well as the permissions in each role, see https://cloud.google.com/iam/help/roles/reference.

§
rolePermission?: "ROLE_PERMISSION_INCLUSION_STATE_UNSPECIFIED" | "ROLE_PERMISSION_INCLUDED" | "ROLE_PERMISSION_NOT_INCLUDED" | "ROLE_PERMISSION_UNKNOWN_INFO"
[src]

Indicates whether the role granted by this role binding contains the specified permission.

§
rolePermissionRelevance?: "HEURISTIC_RELEVANCE_UNSPECIFIED" | "HEURISTIC_RELEVANCE_NORMAL" | "HEURISTIC_RELEVANCE_HIGH"
[src]

The relevance of the permission's existence, or nonexistence, in the role to the overall determination for the entire policy.