Group
The gitlab.GroupProtectedEnvironment resource allows to manage the lifecycle of a protected environment in a group.
In order to use a user_id in the
deploy_access_levelsconfiguration, you need to make sure that users have access to the group with Maintainer role or higher. In order to use a group_id in thedeploy_access_levelsconfiguration, the group_id must be a sub-group under the given group. Upstream API: GitLab REST API docs
Import
Starting in Terraform v1.5.0 you can use an import block to import gitlab_group_protected_environment. For example: terraform import { to = gitlab_group_protected_environment.example id = "see CLI command below for ID" } Import using the CLI is supported using the following syntax: GitLab group protected environments can be imported using an id made up of groupId:environmentName, e.g.
$ pulumi import gitlab:index/groupProtectedEnvironment:GroupProtectedEnvironment 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 deployment tier of the environment. Valid values are production, staging, testing, development, other.