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. This guide focuses on two capabilities: granting roles to multiple members and adding individual members non-authoritatively.

IAM bindings reference existing policy tags and require valid GCP identity principals (users, service accounts, groups, or domains). The examples are intentionally small. Combine them with your own policy tag infrastructure and identity management.

Grant a role to multiple members

Teams managing policy tags 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 PolicyTagIamBinding resource is authoritative for the specified role: it replaces all members for that role on the policy tag. The members array accepts various identity formats including user emails, service accounts, groups, and special identifiers like allAuthenticatedUsers. The policyTag property references the policy tag resource, and role specifies which permission level to grant.

Add a single member to a role

When onboarding individual users or granting access to specific service accounts, teams add members one at a time without affecting existing role assignments.

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 is non-authoritative: it adds a single member to a role without replacing existing members. This approach works well when multiple teams manage access independently. Use member (singular) instead of members (plural) to specify the single identity being granted access.

Beyond these examples

These snippets focus on specific IAM binding features: role-based access control and authoritative vs non-authoritative member management. 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
Policy-level IAM management (PolicyTagIamPolicy)

These omissions are intentional: the goal is to illustrate how each IAM binding approach 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

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

PolicyTagIamPolicy is authoritative for the entire IAM policy and replaces any existing policy. PolicyTagIamBinding is authoritative for a specific role, preserving other roles. PolicyTagIamMember is non-authoritative, adding a single member while preserving other members for that role.

Can I use PolicyTagIamPolicy with PolicyTagIamBinding or PolicyTagIamMember?

No, PolicyTagIamPolicy cannot be used with PolicyTagIamBinding or PolicyTagIamMember as they will conflict over the policy configuration.

Can I use PolicyTagIamBinding and PolicyTagIamMember together?

Yes, but only if they don’t grant privileges to the same role. Each role must be managed by only one resource type.

IAM Configuration

What member identity formats are supported?

The members property supports multiple formats: allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities using principal identifiers.

How do I specify custom roles?

Custom roles must use the full path format: [projects|organizations]/{parent-name}/roles/{role-name}. For example, projects/my-project/roles/my-custom-role.

Immutability & Lifecycle

What properties can't I change after creating a PolicyTagIamBinding?

The policyTag, role, and condition properties are immutable and cannot be changed after creation. You must recreate the resource to modify these values.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides