The gcp:bigqueryanalyticshub/listingIamBinding:ListingIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Analytics Hub listings, controlling which identities can access shared datasets. This guide focuses on two capabilities: granting roles to multiple members and adding individual members to existing roles.
IAM bindings reference existing Analytics Hub listings and operate authoritatively for a given role, meaning they replace all members for that role while preserving other roles. The examples are intentionally small. Combine them with your own listing infrastructure and identity management strategy.
Grant a role to multiple members at once
Teams managing Analytics Hub listings 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.bigqueryanalyticshub.ListingIamBinding("binding", {
project: listing.project,
location: listing.location,
dataExchangeId: listing.dataExchangeId,
listingId: listing.listingId,
role: "roles/viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.bigqueryanalyticshub.ListingIamBinding("binding",
project=listing["project"],
location=listing["location"],
data_exchange_id=listing["dataExchangeId"],
listing_id=listing["listingId"],
role="roles/viewer",
members=["user:jane@example.com"])
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/bigqueryanalyticshub"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := bigqueryanalyticshub.NewListingIamBinding(ctx, "binding", &bigqueryanalyticshub.ListingIamBindingArgs{
Project: pulumi.Any(listing.Project),
Location: pulumi.Any(listing.Location),
DataExchangeId: pulumi.Any(listing.DataExchangeId),
ListingId: pulumi.Any(listing.ListingId),
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.BigQueryAnalyticsHub.ListingIamBinding("binding", new()
{
Project = listing.Project,
Location = listing.Location,
DataExchangeId = listing.DataExchangeId,
ListingId = listing.ListingId,
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.bigqueryanalyticshub.ListingIamBinding;
import com.pulumi.gcp.bigqueryanalyticshub.ListingIamBindingArgs;
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 ListingIamBinding("binding", ListingIamBindingArgs.builder()
.project(listing.project())
.location(listing.location())
.dataExchangeId(listing.dataExchangeId())
.listingId(listing.listingId())
.role("roles/viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:bigqueryanalyticshub:ListingIamBinding
properties:
project: ${listing.project}
location: ${listing.location}
dataExchangeId: ${listing.dataExchangeId}
listingId: ${listing.listingId}
role: roles/viewer
members:
- user:jane@example.com
The role property specifies which permission set to grant (e.g., “roles/viewer”). The members array lists all identities that should receive this role. This resource is authoritative for the specified role, meaning it replaces any existing members for that role while leaving other roles untouched. The dataExchangeId, listingId, and location properties identify which listing to configure.
Add a single member to an existing role
When onboarding individual users or service accounts, teams add them one at a time without affecting other members who already have access.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.bigqueryanalyticshub.ListingIamMember("member", {
project: listing.project,
location: listing.location,
dataExchangeId: listing.dataExchangeId,
listingId: listing.listingId,
role: "roles/viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.bigqueryanalyticshub.ListingIamMember("member",
project=listing["project"],
location=listing["location"],
data_exchange_id=listing["dataExchangeId"],
listing_id=listing["listingId"],
role="roles/viewer",
member="user:jane@example.com")
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/bigqueryanalyticshub"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := bigqueryanalyticshub.NewListingIamMember(ctx, "member", &bigqueryanalyticshub.ListingIamMemberArgs{
Project: pulumi.Any(listing.Project),
Location: pulumi.Any(listing.Location),
DataExchangeId: pulumi.Any(listing.DataExchangeId),
ListingId: pulumi.Any(listing.ListingId),
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.BigQueryAnalyticsHub.ListingIamMember("member", new()
{
Project = listing.Project,
Location = listing.Location,
DataExchangeId = listing.DataExchangeId,
ListingId = listing.ListingId,
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.bigqueryanalyticshub.ListingIamMember;
import com.pulumi.gcp.bigqueryanalyticshub.ListingIamMemberArgs;
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 ListingIamMember("member", ListingIamMemberArgs.builder()
.project(listing.project())
.location(listing.location())
.dataExchangeId(listing.dataExchangeId())
.listingId(listing.listingId())
.role("roles/viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:bigqueryanalyticshub:ListingIamMember
properties:
project: ${listing.project}
location: ${listing.location}
dataExchangeId: ${listing.dataExchangeId}
listingId: ${listing.listingId}
role: roles/viewer
member: user:jane@example.com
The member property (singular) specifies one identity to add. Unlike ListingIamBinding, the ListingIamMember resource is non-authoritative, meaning it adds this member without removing others. You can use multiple ListingIamMember resources for the same role, or combine them with ListingIamBinding resources as long as they target different roles.
Beyond these examples
These snippets focus on specific IAM binding features: role-based access control, bulk member assignment, and incremental member addition. They’re intentionally minimal rather than full access management solutions.
The examples reference pre-existing infrastructure such as Analytics Hub listings (dataExchangeId and listingId) and a GCP project with configured location. They focus on configuring access rather than provisioning the listings themselves.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Policy-level management (ListingIamPolicy resource)
- Custom role definitions
- 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 ListingIamBinding resource reference for all available configuration options.
Let's manage GCP BigQuery Analytics Hub Listing 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
You have three options:
- ListingIamPolicy - Authoritative. Replaces the entire IAM policy for the listing.
- ListingIamBinding - Authoritative for a specific role. Grants a role to multiple members while preserving other roles.
- ListingIamMember - Non-authoritative. Adds a single member to a role while preserving other members.
ListingIamPolicy cannot be used with ListingIamBinding or ListingIamMember because they will conflict over policy management.IAM Configuration
allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, and federated identities (e.g., principal://iam.googleapis.com/...).[projects|organizations]/{parent-name}/roles/{role-name}.Resource Properties
dataExchangeId, listingId, location, project, role, and condition.