entrepot_role
A custom role: a named set of actions that entrepot_role_binding grants to users, groups, GitLab trust policies or all authenticated principals on matching repositories.
The built-in roles (viewer, developer, maintainer, admin) are read-only and cannot be managed with this resource; reference them by name in role bindings (or read them with the entrepot_role data source).
Example Usage
Section titled “Example Usage”# A custom role for CI jobs that publish packages but never delete them.resource "entrepot_role" "publisher" { name = "publisher" description = "Read and upload packages" actions = ["read", "write"]}Schema
Section titled “Schema”Required
Section titled “Required”actions(Set of String) Actions the role grants: any ofread,write(upload/overwrite),deleteandadmin(manage the repository; on repository pattern*it grants system administration).name(String) Role name. Must not be a built-in role name. Changing it forces a new role.
Optional
Section titled “Optional”description(String) Free-form description.
Read-Only
Section titled “Read-Only”id(String) Same asname.
Import
Section titled “Import”The terraform import command can be used, for example:
# Custom roles are imported by name (built-in roles cannot be managed).terraform import entrepot_role.publisher publisherResource documentation generated from the provider’s schema (docs/resources/role.md in terraform-provider-entrepot).