Manage IAM Permissions for GCP Source Repositories

The gcp:sourcerepo/repositoryIamBinding:RepositoryIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for Cloud Source Repositories. It provides authoritative control over which identities have a specific role on a repository. This guide focuses on two capabilities: authoritative role binding for multiple members and incremental member grants.

This resource manages access to an existing repository. The RepositoryIamBinding resource is authoritative for a given role, meaning it replaces all members for that role. Use RepositoryIamMember when you need to add members incrementally without managing the complete list. The examples are intentionally small. Combine them with your own repository and identity management.

Grant a role to multiple members at once

When managing repository access, you often need to grant the same role to multiple users or service accounts simultaneously.

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

const binding = new gcp.sourcerepo.RepositoryIamBinding("binding", {
    project: my_repo.project,
    repository: my_repo.name,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});

import pulumi
import pulumi_gcp as gcp

binding = gcp.sourcerepo.RepositoryIamBinding("binding",
    project=my_repo["project"],
    repository=my_repo["name"],
    role="roles/viewer",
    members=["user:jane@example.com"])

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := sourcerepo.NewRepositoryIamBinding(ctx, "binding", &sourcerepo.RepositoryIamBindingArgs{
			Project:    pulumi.Any(my_repo.Project),
			Repository: pulumi.Any(my_repo.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.SourceRepo.RepositoryIamBinding("binding", new()
    {
        Project = my_repo.Project,
        Repository = my_repo.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.sourcerepo.RepositoryIamBinding;
import com.pulumi.gcp.sourcerepo.RepositoryIamBindingArgs;
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 RepositoryIamBinding("binding", RepositoryIamBindingArgs.builder()
            .project(my_repo.project())
            .repository(my_repo.name())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}

resources:
  binding:
    type: gcp:sourcerepo:RepositoryIamBinding
    properties:
      project: ${["my-repo"].project}
      repository: ${["my-repo"].name}
      role: roles/viewer
      members:
        - user:jane@example.com

The role property specifies which permission set to grant (e.g., “roles/viewer” for read access). The members array lists all identities that should have this role. This resource is authoritative for the specified role: it replaces any existing member list for that role on the repository.

Add a single member to a role incrementally

When you need to grant access to one person without affecting others who already have that role, use RepositoryIamMember for non-authoritative updates.

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

const member = new gcp.sourcerepo.RepositoryIamMember("member", {
    project: my_repo.project,
    repository: my_repo.name,
    role: "roles/viewer",
    member: "user:jane@example.com",
});

import pulumi
import pulumi_gcp as gcp

member = gcp.sourcerepo.RepositoryIamMember("member",
    project=my_repo["project"],
    repository=my_repo["name"],
    role="roles/viewer",
    member="user:jane@example.com")

package main

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

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := sourcerepo.NewRepositoryIamMember(ctx, "member", &sourcerepo.RepositoryIamMemberArgs{
			Project:    pulumi.Any(my_repo.Project),
			Repository: pulumi.Any(my_repo.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.SourceRepo.RepositoryIamMember("member", new()
    {
        Project = my_repo.Project,
        Repository = my_repo.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.sourcerepo.RepositoryIamMember;
import com.pulumi.gcp.sourcerepo.RepositoryIamMemberArgs;
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 RepositoryIamMember("member", RepositoryIamMemberArgs.builder()
            .project(my_repo.project())
            .repository(my_repo.name())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}

resources:
  member:
    type: gcp:sourcerepo:RepositoryIamMember
    properties:
      project: ${["my-repo"].project}
      repository: ${["my-repo"].name}
      role: roles/viewer
      member: user:jane@example.com

The member property (singular) specifies one identity to add. Unlike RepositoryIamBinding, this resource preserves other members who already have the role. Use this when you don’t want to manage the complete member list or when multiple teams manage access independently.

Beyond these examples

These snippets focus on specific IAM binding features: authoritative role binding and incremental member grants. They’re intentionally minimal rather than full access control configurations.

The examples reference pre-existing infrastructure such as a Cloud Source Repositories repository (my_repo). They focus on configuring IAM bindings rather than provisioning the repository itself.

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

Conditional IAM bindings (condition property)
Full policy replacement (RepositoryIamPolicy)
Custom role formats ([projects|organizations]/{parent}/roles/{name})
Federated identity principals and workload identity

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 RepositoryIamBinding resource reference for all available configuration options.

Let's manage IAM Permissions for GCP Source Repositories

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 RepositoryIamPolicy, RepositoryIamBinding, and RepositoryIamMember?

gcp.sourcerepo.RepositoryIamPolicy is fully authoritative and replaces the entire IAM policy. gcp.sourcerepo.RepositoryIamBinding is authoritative for a specific role but preserves other roles. gcp.sourcerepo.RepositoryIamMember is non-authoritative and adds a single member while preserving other members for that role.

Can I use RepositoryIamPolicy together with RepositoryIamBinding or RepositoryIamMember?

No, gcp.sourcerepo.RepositoryIamPolicy cannot be used with gcp.sourcerepo.RepositoryIamBinding or gcp.sourcerepo.RepositoryIamMember because they will conflict over the policy configuration.

Can I use RepositoryIamBinding and RepositoryIamMember together?

Yes, but only if they don’t grant privileges to the same role. Using both on the same role will cause conflicts.

Which IAM resource should I use for my use case?

Use gcp.sourcerepo.RepositoryIamPolicy to manage the complete policy authoritatively. Use gcp.sourcerepo.RepositoryIamBinding to manage all members for a specific role. Use gcp.sourcerepo.RepositoryIamMember to add individual members without affecting others.

Configuration & Identity Management

What member identity formats are supported?

Supported formats include allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner/Editor/Viewer:{projectid}, and federated identities like principal://iam.googleapis.com/....

What properties are immutable after creation?

The role, repository, project, and condition properties are immutable and cannot be changed after the resource is created.

Can I use multiple RepositoryIamBinding resources for the same repository?

Yes, but each gcp.sourcerepo.RepositoryIamBinding must manage a different role. Only one binding per role is allowed.

Custom Roles & Advanced Usage

What format do custom roles require?

Custom roles must use the full format [projects|organizations]/{parent-name}/roles/{role-name}. This applies to both configuration and import operations.

How do I import IAM resources with custom roles?

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

Using a different cloud?

Explore iam guides for other cloud providers:

AWS Guides Azure Guides