Skip to content

git: access-control-list cannot be updated, and the user receives an erroneous "requires replacement" warning if they attempt to do so #1633

Open

Description

@tomkillen

Description

Please add a clear and concise description of what the bug is.

Steps to reproduce

  1. Define a git instance resource
resource "stackit_git" "instance" {
  project_id = var.stackit_project_id
  name       = "cannot-update-acls"
  flavor     = "git-10"
  acl        = [ "0.0.0.0/0" ]
}
  1. Create the instance (apply)
terraform apply
  1. Modify the ACL
resource "stackit_git" "instance" {
  project_id = var.stackit_project_id
  name       = "cannot-update-acls"
  flavor     = "git-10"
  acl        = [ "127.0.0.1/32" ]
}
  1. Update the instance (apply)
terraform apply
  1. Note the "forces replacement" warning

  2. Additionally, if the user proceeds with the apply, nothing actually takes place. The instance is not updated or deleted. Instead an error message informs the user that updating git instances is not supported.

w. First apply (create) a git instance with a terraform block such as

resource "stackit_git" "git_10" {
  project_id = var.stackit_project_id
  name       = "cannot-update-acls"
  flavor     = "git-10"
  acl        = [ "0.0.0.0/0" ]
}

Actual behavior

  1. When the user attempts to update a Git instance access-control-list, the provider warns the user that this will force a replacement of the git instance (1 to destory, 1 to create)
  2. If the user proceeds with the apply, the provider logs an error stating that the update flow is not supported.

Expected behavior

  1. A user should be able to change the access-control-list without this being flagged as a replacement.
  2. The user should be able to update git resources.

Environment

  • OS: darwin_arm64
  • Terraform version (see terraform --version): v1.15.8
  • Version of the STACKIT Terraform provider: v0.106.0

Additional information

Feel free to add any additional information here.

Activity

  1. cgoetz-inovex commented on Aug 13, 2026

    @cgoetz-inovex
    Contributor

    Hi @tomkillen ,

    thanks for notifying us about this. I'll create an internal issue to add the missing update functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions