Update IAM Policy - BlinkOps Documentation

Updates the specified policy. You can update only the rules and the display name for the policy. To update a policy, you should use a read-modify-write loop: 1. Use GetPolicy to read the current version of the policy. 2. Modify the policy as needed. 3. Use UpdatePolicy to write the updated policy. This pattern helps prevent conflicts between concurrent updates.

External DocumentationTo learn more, visit the GCP documentation.

Parameters

Parameter	Description
Annotations	A key-value map to store arbitrary metadata for the `Policy`. Keys can be up to 63 characters. Values can be up to 255 characters.
Display Name	A user-specified description of the `Policy`. This value can be up to 63 characters.
Parent ID	The ID of the parent resource to access. For organizations and folders, must be the numeric ID. For projects, can be the alphanumeric or numeric ID. All action responses contain the numeric ID.
Parent Type	Which type of parent resource to access.
Policy ID	Name of the policy to access. Can be retrieved using the “List IAM Policies” action.
Rules	A list of rules that specify the behavior of the `Policy`. All of the rules should be of the `kind` specified in the `Policy`.

Example Output

{
	"done": false,
	"error": {
		"code": 0,
		"details": [
			{}
		],
		"message": "A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client."
	},
	"metadata": {},
	"name": "The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{unique_id}`.",
	"response": {}
}

Workflow Library Example

Update Iam Policy with Gcp and Send Results Via Email

Preview this Workflow on desktop

​Parameters

​Example Output

​Workflow Library Example

Parameters

Example Output

Workflow Library Example