Project
The gitlab.ProjectProtectedEnvironment resource allows to manage the lifecycle of a protected environment in a project.
In order to use a user or group in the
deploy_access_levelsconfiguration, you need to make sure that users have access to the project and groups must have this project shared. You may use thegitlab.ProjectMembershipandgitlab_project_shared_groupresources to achieve this. Unfortunately, the GitLab API does not complain about users and groups without access to the project and just ignores those. In case this happens you will get perpetual state diffs. Upstream API: GitLab REST API docs
Import
Starting in Terraform v1.5.0 you can use an import block to import gitlab_project_protected_environment. For example: terraform import { to = gitlab_project_protected_environment.example id = "see CLI command below for ID" } Import using the CLI is supported using the following syntax: GitLab protected environments can be imported using an id made up of projectId:environmentName, e.g.
$ pulumi import gitlab:index/projectProtectedEnvironment:ProjectProtectedEnvironment bar 123:productionProperties
Array of approval rules to deploy, with each described by a hash. Elements in the approval_rules should be one of user_id, group_id or access_level.
Array of access levels allowed to deploy, with each described by a hash. Elements in the deploy_access_levels should be one of user_id, group_id or access_level.
The name of the environment.