Member Role Args
The gitlab.MemberRole resource allows to manage the lifecycle of a custom member role. Custom roles allow an organization to create user roles with the precise privileges and permissions required for that organization’s needs.
This resource requires an Ultimate license. Most custom roles are considered billable users that use a seat. Custom roles billing and seat usage There can be only 10 custom roles on your instance or namespace. See issue 450929 for more details. Upstream API: GitLab GraphQL API docs
Constructors
Properties
The base access level for the custom role. Valid values are: DEVELOPER, GUEST, MAINTAINER, MINIMAL_ACCESS, OWNER, REPORTER
Description for the member role.
All permissions enabled for the custom role. Valid values are: ADMIN_CICD_VARIABLES, ADMIN_COMPLIANCE_FRAMEWORK, ADMIN_GROUP_MEMBER, ADMIN_INTEGRATIONS, ADMIN_MERGE_REQUEST, ADMIN_PUSH_RULES, ADMIN_RUNNERS, ADMIN_TERRAFORM_STATE, ADMIN_VULNERABILITY, ADMIN_WEB_HOOK, ARCHIVE_PROJECT, MANAGE_DEPLOY_TOKENS, MANAGE_GROUP_ACCESS_TOKENS, MANAGE_MERGE_REQUEST_SETTINGS, MANAGE_PROJECT_ACCESS_TOKENS, MANAGE_SECURITY_POLICY_LINK, READ_CODE, READ_CRM_CONTACT, READ_DEPENDENCY, READ_RUNNERS, READ_VULNERABILITY, REMOVE_GROUP, REMOVE_PROJECT