Perun-Engineering · wiseelf · Jul 7, 2026 · Jul 7, 2026 · Jul 7, 2026 · Jul 7, 2026
diff --git a/Readme.md b/Readme.md
@@ -15,8 +15,8 @@ This Terraform module provides resources to manage GitLab groups, projects, inte
 
 ## Requirements
 
-- Terraform 1.5.7 or higher.
-- GitLab Provider for Terraform 18.0.0 or higher.
+- Terraform 1.8.0 or higher.
+- GitLab Provider for Terraform 19.0.0 or higher. See [docs/UPGRADE-2.0.md](docs/UPGRADE-2.0.md) if upgrading from a 18.x-based release of this module.
 
 ## Usage
 
@@ -111,13 +111,13 @@ The module provides the following outputs:
 
 You can find examples in the examples/ directory for different use cases, such as managing multiple groups, configuring integrations, and using different YAML configurations.
 
-- [terraform](https://github.com/opsworks-co/terraform-gitlab/tree/main/examples/terraform) - How to use module with terraform
-- [terragrunt](https://github.com/opsworks-co/terraform-gitlab/tree/main/examples/terragrunt) - How to use module with terragrunt
+- [terraform](https://github.com/Perun-Engineering/terraform-gitlab/tree/main/examples/terraform) - How to use module with terraform
+- [terragrunt](https://github.com/Perun-Engineering/terraform-gitlab/tree/main/examples/terragrunt) - How to use module with terragrunt
 
 ## Authors
 
 Module is maintained by [Serhii Kaidalov](https://github.com/wiseelf).
 
 ## License
 
-Apache 2 Licensed. See [LICENSE](https://github.com/opsworks-co/terraform-gitlab/tree/main/LICENSE) for full details.
+Apache 2 Licensed. See [LICENSE](https://github.com/Perun-Engineering/terraform-gitlab/tree/main/LICENSE) for full details.
diff --git a/docs/UPGRADE-2.0.md b/docs/UPGRADE-2.0.md
@@ -0,0 +1,82 @@
+# Upgrade to 2.x
+
+This update bumps the GitLab provider requirement from `18.4.1` to `19.1.0` to pick up
+GitLab 19.0 support. The provider's own [19.0 upgrade guide](https://registry.terraform.io/providers/gitlabhq/gitlab/latest/docs/guides/version-19.0-upgrade)
+required matching changes in this module.
+
+Requires Terraform `>= 1.8` (needed for the `moved` blocks in `moved.tf`, which move
+resources across different resource types).
+
+## Resource renames (handled automatically by `moved.tf`)
+
+- `gitlab_project_mirror` -> `gitlab_project_push_mirror`
+- `gitlab_integration_emails_on_push` -> `gitlab_project_integration_emails_on_push`
+- `gitlab_integration_external_wiki` -> `gitlab_project_integration_external_wiki`
+- `gitlab_integration_github` -> `gitlab_project_integration_github`
+- `gitlab_integration_jira` -> `gitlab_project_integration_jira`
+- `gitlab_integration_microsoft_teams` -> `gitlab_project_integration_microsoft_teams`
+- `gitlab_integration_pipelines_email` -> `gitlab_project_integration_pipelines_email`
+
+No action needed for these; `terraform plan` will show them moved in place.
+
+## Resource splits (require a manual `terraform state mv`)
+
+Terraform rejects two `moved` blocks that share the same `from` address with
+`Error: Ambiguous move statements`, even when the destination `for_each` sets are
+disjoint — so these two splits can't be automated in `moved.tf`. Without a manual
+move, `terraform plan` will destroy the old resource and create the new one.
+
+### `gitlab_deploy_token` -> `gitlab_project_deploy_token` / `gitlab_group_deploy_token`
+
+Move each instance to the resource matching its scope (`project` vs `group` in your
+`gitlab_deploy_token.this` addresses):
+
+```bash
+terraform state mv 'module.gitlab.gitlab_deploy_token.this["project-ns-proj-mytoken"]' 'module.gitlab.gitlab_project_deploy_token.this["project-ns-proj-mytoken"]'
+terraform state mv 'module.gitlab.gitlab_deploy_token.this["group-mygroup-mytoken"]'   'module.gitlab.gitlab_group_deploy_token.this["group-mygroup-mytoken"]'
+```
+
+### `gitlab_branch_protection` -> `.ce` / `.ee`
+
+Move each instance to `.ce` if your `var.tier` is `free`, or `.ee` if `premium`/`ultimate`:
+
+```bash
+# tier = "free"
+terraform state mv 'module.gitlab.gitlab_branch_protection.this["ns-proj-main"]' 'module.gitlab.gitlab_branch_protection.ce["ns-proj-main"]'
+
+# tier = "premium" / "ultimate"
+terraform state mv 'module.gitlab.gitlab_branch_protection.this["ns-proj-main"]' 'module.gitlab.gitlab_branch_protection.ee["ns-proj-main"]'
+```
+
+## ⚠️ Breaking changes to `gitlab_projects` input
+
+The following keys on a project entry no longer have any effect, because the provider
+removed the underlying attributes. Use the replacement listed instead:
+
+| Removed key | Replacement |
+|---|---|
+| `issues_enabled` | `issues_access_level` (`"enabled"` / `"disabled"`) |
+| `merge_requests_enabled` | `merge_requests_access_level` |
+| `wiki_enabled` | `wiki_access_level` |
+| `snippets_enabled` | `snippets_access_level` |
+| `restrict_user_defined_variables` | `ci_pipeline_variables_minimum_override_role` (`false` -> `"developer"`, `true` -> `"maintainer"`) |
+| `tags` | `topics` |
+| `import_url`, `import_url_username`, `import_url_password`, `mirror_trigger_builds`, `only_mirror_protected_branches`, `mirror_overwrites_diverged_branches` | still supported, but now provisioned via a new `gitlab_project_pull_mirror` resource instead of `gitlab_project` attributes. Set `mirror: true` and `import_url` on the project as before. |
+| `settings.level_mr_approvals[].require_password_to_approve` | `require_reauthentication_to_approve` (same meaning, provider-deprecated key removed in GitLab 20.0) |
+
+## `gitlab_branch_protection` (CE vs EE)
+
+The provider no longer allows `push_access_level`/`merge_access_level`/`unprotect_access_level`
+and `allowed_to_push`/`allowed_to_merge`/`allowed_to_unprotect` on the same resource. This module
+now picks the correct resource automatically based on `var.tier`:
+
+- `tier = "free"` -> CE resource, honors `push_access_level` / `merge_access_level` on a branch.
+- `tier = "premium"` / `"ultimate"` -> EE resource, honors `allowed_to_push` / `allowed_to_merge` /
+  `allowed_to_unprotect` / `code_owner_approval_required` on a branch. `unprotect_access_level` is
+  no longer configurable in either mode (removed by the provider).
+
+## `gitlab_project_protected_environment`
+
+`deploy_access_levels` blocks were replaced by a single `deploy_access_levels_attribute` list.
+No input schema changes; `project.settings.protected_environments[].deploy_access_levels` is
+unchanged.
diff --git a/examples/terraform/versions.tf b/examples/terraform/versions.tf
@@ -2,8 +2,8 @@ terraform {
   required_providers {
     gitlab = {
       source  = "gitlabhq/gitlab"
-      version = ">= 17.3.0"
+      version = ">= 19.0.0"
     }
   }
-  required_version = ">= 1.3.0"
+  required_version = ">= 1.8.0"
 }
diff --git a/examples/terragrunt/gitlab/terragrunt.hcl b/examples/terragrunt/gitlab/terragrunt.hcl
@@ -1,5 +1,5 @@
 terraform {
-  #source = "git@github.com:opsworks-co/terraform-gitlab.git//.?ref=${include.root.locals.terraform-gitlab}"
+  #source = "git@github.com:Perun-Engineering/terraform-gitlab.git//.?ref=${include.root.locals.terraform-gitlab}"
   source = get_repo_root()
 }
 

diff --git a/examples/terragrunt/terragrunt.hcl b/examples/terragrunt/terragrunt.hcl
@@ -2,11 +2,11 @@ locals {
   # iam_role     = "arn:aws:iam::012345678912:role/terragrunt"
   # session_name = "gitlab-terragrunt-012345678912"
   # Modules version (sorted a-z)
-  terraform-gitlab = "v0.1.0" # https://github.com/opsworks-co/terraform-gitlab
+  terraform-gitlab = "v1.4.0" # https://github.com/Perun-Engineering/terraform-gitlab
 }
 
-terraform_version_constraint  = "= 1.5.7"
-terragrunt_version_constraint = "= 0.67.1"
+terraform_version_constraint  = ">= 1.8.0"
+terragrunt_version_constraint = "= 0.99.5"
 # iam_role                      = local.iam_role
 
 # Configure Terragrunt to automatically store tfstate files in an S3 bucket