runr_project_access (Resource)

A role for a user or a group on one project only (project access). The role's project-scoped permissions apply to that project; organization-wide roles cover every project already. Needs projects.manage_access on the project. A user or group holds one role per project: a second resource for the same subject changes the role of the same grant.

Example Usage#

# A role on one project only, for a user ...
resource "runr_project_access" "grace" {
  project_id = runr_project.orders.id
  user       = "grace@example.com" # user id, e-mail address or username
  role       = "developer"
}

# ... or for a group.
resource "runr_project_access" "auditors" {
  project_id = runr_project.orders.id
  group_id   = runr_group.auditors.id
  role       = "viewer"
}

Schema#

Required#

project_id (String) Project id.
role (String) Role key on the project (built-in such as developer or viewer, or runr_role.<name>.key). The Owner role is given to members directly only.

Optional#

group_id (String) The group (runr_group.<name>.id).
user (String) The user, by id, e-mail address or username. Exactly one of user and group_id.

Read-Only#

id (String) Grant id.
subject_id (String) User or group id.
subject_type (String) user or group.

Import#

Import is supported using the following syntax:

The terraform import command can be used, for example:

# <project name or id>/<grant id> (`runr access ls -p <project>` lists the grant ids)
terraform import runr_project_access.grace orders-api/01JABCDEF0123456789ABCDEFG