The gcp:datacatalog/entryGroupIamBinding:EntryGroupIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Data Catalog entry groups by granting a specific role to a list of members. This guide focuses on two capabilities: binding roles to multiple members and adding individual members incrementally.
This resource is authoritative for a given role, meaning it replaces the entire member list for that role. It can be used alongside EntryGroupIamMember resources as long as they don’t manage the same role. The examples are intentionally small. Combine them with your own entry groups and identity management workflows.
Grant a role to multiple members at once
Teams managing entry groups often need to grant the same role to multiple users or service accounts simultaneously, such as giving viewer access to an entire team.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const binding = new gcp.datacatalog.EntryGroupIamBinding("binding", {
entryGroup: basicEntryGroup.name,
role: "roles/viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.datacatalog.EntryGroupIamBinding("binding",
entry_group=basic_entry_group["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.NewEntryGroupIamBinding(ctx, "binding", &datacatalog.EntryGroupIamBindingArgs{
EntryGroup: pulumi.Any(basicEntryGroup.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.EntryGroupIamBinding("binding", new()
{
EntryGroup = basicEntryGroup.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.EntryGroupIamBinding;
import com.pulumi.gcp.datacatalog.EntryGroupIamBindingArgs;
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 EntryGroupIamBinding("binding", EntryGroupIamBindingArgs.builder()
.entryGroup(basicEntryGroup.name())
.role("roles/viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:datacatalog:EntryGroupIamBinding
properties:
entryGroup: ${basicEntryGroup.name}
role: roles/viewer
members:
- user:jane@example.com
The entryGroup property references the entry group to bind permissions to. The role property specifies which IAM role to grant. The members array lists all identities that should receive this role. This resource is authoritative for the specified role, replacing any existing member list for that role on the entry group.
Add a single member to a role incrementally
When onboarding individual users or service accounts, you can grant access without affecting existing members who already have that role.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.datacatalog.EntryGroupIamMember("member", {
entryGroup: basicEntryGroup.name,
role: "roles/viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.datacatalog.EntryGroupIamMember("member",
entry_group=basic_entry_group["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.NewEntryGroupIamMember(ctx, "member", &datacatalog.EntryGroupIamMemberArgs{
EntryGroup: pulumi.Any(basicEntryGroup.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.EntryGroupIamMember("member", new()
{
EntryGroup = basicEntryGroup.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.EntryGroupIamMember;
import com.pulumi.gcp.datacatalog.EntryGroupIamMemberArgs;
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 EntryGroupIamMember("member", EntryGroupIamMemberArgs.builder()
.entryGroup(basicEntryGroup.name())
.role("roles/viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:datacatalog:EntryGroupIamMember
properties:
entryGroup: ${basicEntryGroup.name}
role: roles/viewer
member: user:jane@example.com
The member property (singular) adds one identity to the role. Unlike EntryGroupIamBinding, this resource is non-authoritative, preserving other members already assigned to the role. Use this when you need to add access incrementally without managing the complete member list.
Beyond these examples
These snippets focus on specific IAM binding features: role binding with multiple members and incremental member addition. They’re intentionally minimal rather than full access control configurations.
The examples reference pre-existing infrastructure such as Data Catalog entry groups. They focus on configuring IAM bindings rather than provisioning the entry groups themselves.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Explicit project and region specification
- Policy-level IAM management (EntryGroupIamPolicy)
- Custom role formatting for organizations
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 EntryGroupIamBinding resource reference for all available configuration options.
Let's manage GCP Data Catalog Entry Group IAM Bindings
Get started with Pulumi Cloud, then follow our quick setup guide to deploy this infrastructure.
Try Pulumi Cloud for FREEFrequently Asked Questions
Resource Selection & Conflicts
gcp.datacatalog.EntryGroupIamPolicy is authoritative and replaces the entire policy, gcp.datacatalog.EntryGroupIamBinding is authoritative for a specific role while preserving other roles, and gcp.datacatalog.EntryGroupIamMember is non-authoritative and preserves other members for the same role.gcp.datacatalog.EntryGroupIamPolicy cannot be used with gcp.datacatalog.EntryGroupIamBinding or gcp.datacatalog.EntryGroupIamMember because they will conflict over the policy configuration.Configuration & Member Identities
allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, and federated identities like principal://iam.googleapis.com/....entryGroup, role, project, region, and condition properties are immutable and cannot be modified after the resource is created.Import & Custom Roles
[projects|organizations]/{parent-name}/roles/{role-name}, for example projects/my-project/roles/my-custom-role.pulumi import gcp:datacatalog/entryGroupIamBinding:EntryGroupIamBinding editor "projects/{{project}}/locations/{{region}}/entryGroups/{{entry_group}} roles/viewer".