AddressGroupIamPolicyArgs

Three different resources help you manage your IAM policy for Network Security ProjectAddressGroup. Each of these resources serves a different use case:

• gcp.networksecurity.AddressGroupIamPolicy: Authoritative. Sets the IAM policy for the projectaddressgroup and replaces any existing policy already attached.

• gcp.networksecurity.AddressGroupIamBinding: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the projectaddressgroup are preserved.

• gcp.networksecurity.AddressGroupIamMember: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the projectaddressgroup are preserved. A data source can be used to retrieve policy data in advent you do not need creation

• gcp.networksecurity.AddressGroupIamPolicy: Retrieves the IAM policy for the projectaddressgroup

Note: gcp.networksecurity.AddressGroupIamPolicy cannot be used in conjunction with gcp.networksecurity.AddressGroupIamBinding and gcp.networksecurity.AddressGroupIamMember or they will fight over what your policy should be. Note: gcp.networksecurity.AddressGroupIamBinding resources can be used in conjunction with gcp.networksecurity.AddressGroupIamMember resources only if they do not grant privilege to the same role.

Import

For all import syntaxes, the "resource in question" can take any of the following forms:

• projects/{{project}}/locations/{{location}}/addressGroups/{{name}}

• {{project}}/{{location}}/{{name}}

• {{location}}/{{name}}

• {{name}} Any variables not passed in the import command will be taken from the provider configuration. Network Security projectaddressgroup IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.

$ pulumi import gcp:networksecurity/addressGroupIamPolicy:AddressGroupIamPolicy editor "projects/{{project}}/locations/{{location}}/addressGroups/{{project_address_group}} roles/compute.networkAdmin user:jane@example.com"

IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g.

$ pulumi import gcp:networksecurity/addressGroupIamPolicy:AddressGroupIamPolicy editor "projects/{{project}}/locations/{{location}}/addressGroups/{{project_address_group}} roles/compute.networkAdmin"

IAM policy imports use the identifier of the resource in question, e.g.

$ pulumi import gcp:networksecurity/addressGroupIamPolicy:AddressGroupIamPolicy editor projects/{{project}}/locations/{{location}}/addressGroups/{{project_address_group}}

->Custom Roles If you're importing a IAM resource with a custom role, make sure to use the full name of the custom role, e.g. [projects/my-project|organizations/my-org]/roles/my-custom-role.