Manage GCP Data Catalog Policy Tag IAM Bindings

The gcp:datacatalog/policyTagIamBinding:PolicyTagIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Data Catalog policy tags. It grants roles to lists of members while preserving other roles on the same policy tag. This guide focuses on two capabilities: granting roles to multiple members and adding individual members non-authoritatively.

IAM bindings reference existing policy tags and grant access to Google identities such as users, service accounts, and groups. The examples are intentionally small. Combine them with your own policy tag infrastructure and identity management.

Grant a role to multiple members

Teams managing data governance often grant the same role to multiple users or service accounts at once, ensuring consistent access across a group.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const binding = new gcp.datacatalog.PolicyTagIamBinding("binding", {
    policyTag: basicPolicyTag.name,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});

import pulumi
import pulumi_gcp as gcp

binding = gcp.datacatalog.PolicyTagIamBinding("binding",
    policy_tag=basic_policy_tag["name"],
    role="roles/viewer",
    members=["user:jane@example.com"])

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/datacatalog"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := datacatalog.NewPolicyTagIamBinding(ctx, "binding", &datacatalog.PolicyTagIamBindingArgs{
			PolicyTag: pulumi.Any(basicPolicyTag.Name),
			Role:      pulumi.String("roles/viewer"),
			Members: pulumi.StringArray{
				pulumi.String("user:jane@example.com"),
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var binding = new Gcp.DataCatalog.PolicyTagIamBinding("binding", new()
    {
        PolicyTag = basicPolicyTag.Name,
        Role = "roles/viewer",
        Members = new[]
        {
            "user:jane@example.com",
        },
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.datacatalog.PolicyTagIamBinding;
import com.pulumi.gcp.datacatalog.PolicyTagIamBindingArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var binding = new PolicyTagIamBinding("binding", PolicyTagIamBindingArgs.builder()
            .policyTag(basicPolicyTag.name())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}

resources:
  binding:
    type: gcp:datacatalog:PolicyTagIamBinding
    properties:
      policyTag: ${basicPolicyTag.name}
      role: roles/viewer
      members:
        - user:jane@example.com

The binding resource is authoritative for the specified role: it replaces all members for that role on the policy tag. The policyTag property identifies the target resource, role specifies which permission to grant, and members lists all identities that receive the role. Other roles on the same policy tag remain unchanged.

Add a single member to a role

When onboarding individual users or granting access to specific service accounts, non-authoritative member grants preserve existing access while adding new identities.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const member = new gcp.datacatalog.PolicyTagIamMember("member", {
    policyTag: basicPolicyTag.name,
    role: "roles/viewer",
    member: "user:jane@example.com",
});

import pulumi
import pulumi_gcp as gcp

member = gcp.datacatalog.PolicyTagIamMember("member",
    policy_tag=basic_policy_tag["name"],
    role="roles/viewer",
    member="user:jane@example.com")

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/datacatalog"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := datacatalog.NewPolicyTagIamMember(ctx, "member", &datacatalog.PolicyTagIamMemberArgs{
			PolicyTag: pulumi.Any(basicPolicyTag.Name),
			Role:      pulumi.String("roles/viewer"),
			Member:    pulumi.String("user:jane@example.com"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var member = new Gcp.DataCatalog.PolicyTagIamMember("member", new()
    {
        PolicyTag = basicPolicyTag.Name,
        Role = "roles/viewer",
        Member = "user:jane@example.com",
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.datacatalog.PolicyTagIamMember;
import com.pulumi.gcp.datacatalog.PolicyTagIamMemberArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var member = new PolicyTagIamMember("member", PolicyTagIamMemberArgs.builder()
            .policyTag(basicPolicyTag.name())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}

resources:
  member:
    type: gcp:datacatalog:PolicyTagIamMember
    properties:
      policyTag: ${basicPolicyTag.name}
      role: roles/viewer
      member: user:jane@example.com

The PolicyTagIamMember resource adds one identity to a role without affecting other members. Use member (singular) instead of members (plural) to specify a single identity. This approach works alongside PolicyTagIamBinding resources as long as they don’t manage the same role.

Beyond these examples

These snippets focus on specific IAM binding features: role bindings for multiple members and individual member grants. They’re intentionally minimal rather than full access control configurations.

The examples reference pre-existing infrastructure such as Data Catalog policy tags. They focus on configuring IAM bindings rather than provisioning the underlying policy tag resources.

To keep things focused, common IAM patterns are omitted, including:

Conditional IAM bindings (condition property)
Custom role definitions
Full IAM policy replacement (PolicyTagIamPolicy)
Federated identity configuration

These omissions are intentional: the goal is to illustrate how each IAM binding feature is wired, not provide drop-in access control modules. See the PolicyTagIamBinding resource reference for all available configuration options.

Let's manage GCP Data Catalog Policy Tag IAM Bindings

Get started with Pulumi Cloud, then follow our quick setup guide to deploy this infrastructure.

Try Pulumi Cloud for FREE

Frequently Asked Questions

Resource Selection & Conflicts

Why am I getting conflicts between my IAM resources?

PolicyTagIamPolicy cannot be used with PolicyTagIamBinding or PolicyTagIamMember because they’ll conflict over the policy. Use PolicyTagIamPolicy alone for full control, or use PolicyTagIamBinding/PolicyTagIamMember for granular management.

Can I use PolicyTagIamBinding and PolicyTagIamMember together?

Yes, but only if they grant different roles. Using both for the same role causes conflicts.

What's the difference between PolicyTagIamPolicy, PolicyTagIamBinding, and PolicyTagIamMember?

PolicyTagIamPolicy is fully authoritative and replaces the entire policy. PolicyTagIamBinding is authoritative for a specific role but preserves other roles. PolicyTagIamMember is non-authoritative and adds a single member to a role while preserving other members.

Configuration & Identity Formats

What member identity formats are supported?

You can use:

user:{email} for Google accounts
serviceAccount:{email} for service accounts
group:{email} for Google groups
domain:{domain} for G Suite domains
allUsers or allAuthenticatedUsers for broad access
projectOwner/Editor/Viewer:{projectid} for project roles
principal://... for federated identities

How do I specify custom roles?

Use the full name format: [projects|organizations]/{parent-name}/roles/{role-name}. For example, projects/my-project/roles/my-custom-role or organizations/my-org/roles/my-custom-role.

Immutability & Lifecycle

What properties can't I change after creation?

The policyTag, role, and condition properties are immutable. Changing them requires recreating the resource.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides