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 controls which identities (users, service accounts, groups) can access a repository. This guide focuses on two capabilities: authoritative role binding and non-authoritative member addition.

This resource manages access to an existing repository. It works alongside RepositoryIamMember when you need to grant different roles independently. The examples are intentionally small. Combine them with your own repository and identity management strategy.

Grant a role to multiple members at once

Teams managing repository access often need to grant the same role to multiple users, service accounts, or groups 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 RepositoryIamBinding resource is authoritative for the specified role. It replaces all existing members for that role with the members list you provide. The role property specifies which permission set to grant (e.g., roles/viewer for read access). The members array accepts various identity formats: user emails, service accounts, groups, or special identifiers like allAuthenticatedUsers.

Add a single member to a role incrementally

When multiple teams manage access independently, non-authoritative member grants prevent conflicts.

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 RepositoryIamMember resource adds one identity without affecting other members of the same role. Use member (singular) instead of members (plural) to specify a single identity. This approach is safe when different Pulumi stacks or teams manage access to the same repository, since each RepositoryIamMember resource operates independently.

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 a Cloud Source Repositories repository (by name and project). They focus on configuring access 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 resource)
Custom role definitions
Federated identity configuration

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?

RepositoryIamPolicy is authoritative and replaces the entire IAM policy. RepositoryIamBinding is authoritative for a specific role, preserving other roles. RepositoryIamMember is non-authoritative, adding individual members while preserving existing members for that role.

Can I use RepositoryIamPolicy with RepositoryIamBinding or RepositoryIamMember?

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

Can I use RepositoryIamBinding with RepositoryIamMember?

Yes, but only if they don’t grant privilege to the same role. If they target the same role, they will conflict.

Why am I getting an error about multiple Bindings for the same role?

Only one RepositoryIamBinding can be used per role. Use a single Binding with multiple members, or switch to RepositoryIamMember for individual member management.

Configuration & Identity Formats

What member identity formats are supported?

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

How do I specify custom roles?

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

Immutability & Limitations

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

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

Using a different cloud?

Explore iam guides for other cloud providers:

AWS Guides Azure Guides