The gcp:containeranalysis/noteIamMember:NoteIamMember resource, part of the Pulumi GCP provider, manages IAM permissions for Container Analysis notes, controlling who can view or modify vulnerability and compliance metadata. This guide focuses on three approaches: authoritative policy replacement, role-level binding, and incremental member addition.
These resources reference existing Container Analysis notes and require the Container Analysis API enabled in your project. The examples are intentionally small. Combine them with your own note resources and identity management.
Replace the entire IAM policy for a note
When you need complete control over note access, define the entire IAM policy from scratch.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const admin = gcp.organizations.getIAMPolicy({
bindings: [{
role: "roles/containeranalysis.notes.occurrences.viewer",
members: ["user:jane@example.com"],
}],
});
const policy = new gcp.containeranalysis.NoteIamPolicy("policy", {
project: note.project,
note: note.name,
policyData: admin.then(admin => admin.policyData),
});
import pulumi
import pulumi_gcp as gcp
admin = gcp.organizations.get_iam_policy(bindings=[{
"role": "roles/containeranalysis.notes.occurrences.viewer",
"members": ["user:jane@example.com"],
}])
policy = gcp.containeranalysis.NoteIamPolicy("policy",
project=note["project"],
note=note["name"],
policy_data=admin.policy_data)
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/containeranalysis"
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/organizations"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
admin, err := organizations.LookupIAMPolicy(ctx, &organizations.LookupIAMPolicyArgs{
Bindings: []organizations.GetIAMPolicyBinding{
{
Role: "roles/containeranalysis.notes.occurrences.viewer",
Members: []string{
"user:jane@example.com",
},
},
},
}, nil)
if err != nil {
return err
}
_, err = containeranalysis.NewNoteIamPolicy(ctx, "policy", &containeranalysis.NoteIamPolicyArgs{
Project: pulumi.Any(note.Project),
Note: pulumi.Any(note.Name),
PolicyData: pulumi.String(admin.PolicyData),
})
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 admin = Gcp.Organizations.GetIAMPolicy.Invoke(new()
{
Bindings = new[]
{
new Gcp.Organizations.Inputs.GetIAMPolicyBindingInputArgs
{
Role = "roles/containeranalysis.notes.occurrences.viewer",
Members = new[]
{
"user:jane@example.com",
},
},
},
});
var policy = new Gcp.ContainerAnalysis.NoteIamPolicy("policy", new()
{
Project = note.Project,
Note = note.Name,
PolicyData = admin.Apply(getIAMPolicyResult => getIAMPolicyResult.PolicyData),
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.organizations.OrganizationsFunctions;
import com.pulumi.gcp.organizations.inputs.GetIAMPolicyArgs;
import com.pulumi.gcp.containeranalysis.NoteIamPolicy;
import com.pulumi.gcp.containeranalysis.NoteIamPolicyArgs;
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) {
final var admin = OrganizationsFunctions.getIAMPolicy(GetIAMPolicyArgs.builder()
.bindings(GetIAMPolicyBindingArgs.builder()
.role("roles/containeranalysis.notes.occurrences.viewer")
.members("user:jane@example.com")
.build())
.build());
var policy = new NoteIamPolicy("policy", NoteIamPolicyArgs.builder()
.project(note.project())
.note(note.name())
.policyData(admin.policyData())
.build());
}
}
resources:
policy:
type: gcp:containeranalysis:NoteIamPolicy
properties:
project: ${note.project}
note: ${note.name}
policyData: ${admin.policyData}
variables:
admin:
fn::invoke:
function: gcp:organizations:getIAMPolicy
arguments:
bindings:
- role: roles/containeranalysis.notes.occurrences.viewer
members:
- user:jane@example.com
NoteIamPolicy is authoritative: it replaces any existing policy on the note. The getIAMPolicy data source constructs the policy document with bindings that map roles to members. Use this when you want to manage all permissions in one place, but be aware it will remove any bindings not declared in your policy.
Grant a role to multiple members at once
When multiple identities need the same access level, bind them all to a role together.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const binding = new gcp.containeranalysis.NoteIamBinding("binding", {
project: note.project,
note: note.name,
role: "roles/containeranalysis.notes.occurrences.viewer",
members: ["user:jane@example.com"],
});
import pulumi
import pulumi_gcp as gcp
binding = gcp.containeranalysis.NoteIamBinding("binding",
project=note["project"],
note=note["name"],
role="roles/containeranalysis.notes.occurrences.viewer",
members=["user:jane@example.com"])
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/containeranalysis"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := containeranalysis.NewNoteIamBinding(ctx, "binding", &containeranalysis.NoteIamBindingArgs{
Project: pulumi.Any(note.Project),
Note: pulumi.Any(note.Name),
Role: pulumi.String("roles/containeranalysis.notes.occurrences.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.ContainerAnalysis.NoteIamBinding("binding", new()
{
Project = note.Project,
Note = note.Name,
Role = "roles/containeranalysis.notes.occurrences.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.containeranalysis.NoteIamBinding;
import com.pulumi.gcp.containeranalysis.NoteIamBindingArgs;
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 NoteIamBinding("binding", NoteIamBindingArgs.builder()
.project(note.project())
.note(note.name())
.role("roles/containeranalysis.notes.occurrences.viewer")
.members("user:jane@example.com")
.build());
}
}
resources:
binding:
type: gcp:containeranalysis:NoteIamBinding
properties:
project: ${note.project}
note: ${note.name}
role: roles/containeranalysis.notes.occurrences.viewer
members:
- user:jane@example.com
NoteIamBinding manages all members for a specific role. It’s authoritative for that role but preserves other roles in the policy. The members array accepts user accounts, service accounts, groups, and special identifiers like allUsers. This approach works well when you manage teams or groups that share permissions.
Add a single member to a role incrementally
When you need to grant access to one identity without affecting others, add them individually.
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";
const member = new gcp.containeranalysis.NoteIamMember("member", {
project: note.project,
note: note.name,
role: "roles/containeranalysis.notes.occurrences.viewer",
member: "user:jane@example.com",
});
import pulumi
import pulumi_gcp as gcp
member = gcp.containeranalysis.NoteIamMember("member",
project=note["project"],
note=note["name"],
role="roles/containeranalysis.notes.occurrences.viewer",
member="user:jane@example.com")
package main
import (
"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/containeranalysis"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := containeranalysis.NewNoteIamMember(ctx, "member", &containeranalysis.NoteIamMemberArgs{
Project: pulumi.Any(note.Project),
Note: pulumi.Any(note.Name),
Role: pulumi.String("roles/containeranalysis.notes.occurrences.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.ContainerAnalysis.NoteIamMember("member", new()
{
Project = note.Project,
Note = note.Name,
Role = "roles/containeranalysis.notes.occurrences.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.containeranalysis.NoteIamMember;
import com.pulumi.gcp.containeranalysis.NoteIamMemberArgs;
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 NoteIamMember("member", NoteIamMemberArgs.builder()
.project(note.project())
.note(note.name())
.role("roles/containeranalysis.notes.occurrences.viewer")
.member("user:jane@example.com")
.build());
}
}
resources:
member:
type: gcp:containeranalysis:NoteIamMember
properties:
project: ${note.project}
note: ${note.name}
role: roles/containeranalysis.notes.occurrences.viewer
member: user:jane@example.com
NoteIamMember is non-authoritative: it adds one member to a role without removing existing members. The member property accepts the same identity formats as NoteIamBinding but manages only a single identity. This is the safest approach when multiple teams manage access independently, since resources won’t conflict as long as they target different members.
Beyond these examples
These snippets focus on specific IAM management features: authoritative and non-authoritative access control, and role-based and member-based permission grants. They’re intentionally minimal rather than full access management solutions.
The examples reference pre-existing infrastructure such as Container Analysis notes and a GCP project with the Container Analysis API enabled. They focus on configuring IAM permissions rather than provisioning the underlying resources.
To keep things focused, common IAM patterns are omitted, including:
- Conditional IAM bindings (condition property)
- Custom role definitions
- Service account creation and management
- Note resource creation and configuration
These omissions are intentional: the goal is to illustrate how each IAM resource type is wired, not provide drop-in access control modules. See the Container Analysis NoteIamMember resource reference for all available configuration options.
Let's manage GCP Container Analysis Note IAM Members
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
NoteIamPolicy cannot be used with NoteIamBinding or NoteIamMember as they will conflict. However, NoteIamBinding and NoteIamMember can be used together only if they grant different roles.NoteIamPolicy is authoritative and replaces the entire IAM policy. NoteIamBinding is authoritative for a specific role and preserves other roles. NoteIamMember is non-authoritative and adds a single member while preserving other members for that role.NoteIamPolicy with NoteIamBinding or NoteIamMember causes conflicts. Choose either the authoritative NoteIamPolicy or the non-authoritative NoteIamBinding/NoteIamMember approach, not both.Configuration & Identity Formats
allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:{projectid}, projectEditor:{projectid}, projectViewer:{projectid}, or federated identities like principal://iam.googleapis.com/....[projects|organizations]/{parent-name}/roles/{role-name}.Immutability & Updates
member, note, project, role, and condition. Changes to any of these require resource replacement.