confluent_environment unable to reflect current Stream governance package

[mihdih]

As introduced in around version 1.7 (I think) of terraform confluent provider, Stream governance is handled under the resource confluent_environment. We are in a situation where our Environments are provisioned using an older version of the provider (1.6.x). When we try to update it now to version 2.2.x, we thought that it would be able to pickup the configured Stream Governance package, given our terraform code is updated.

Current package is set to Essentials

# Old code
resource "confluent_environment" "env-foo" {
  display_name = "foo-environment"

  lifecycle {
    prevent_destroy = true
  }
}

Then updated to

# New code
resource "confluent_environment" "env-foo" {
  display_name = "foo-environment"

  stream_governance {
    package = "ESSENTIALS"
  }

  lifecycle {
    prevent_destroy = true
  }
}

Given that terraform refresh is ran, we thought and would have expected that when running terraform plan/apply no change is detected since code is reflecting the current state.

# confluent_environment.env-foo will be updated in-place
  ~ resource "confluent_environment" "env-foo" {
        id            = "env-xxxx"
        # (2 unchanged attributes hidden)
      ~ stream_governance {
          + package = "ESSENTIALS"
        }
    }

Even if removing the state manually and then re-import, the behaviour still persist. It's as if the API is not returning and reflecting the current state.

[linouk23]

@mihdih thanks for creating this issue!

"We are going to update the backend to return ESSENTIALS for all environments that were created with an old version of the TF Provider (currently, the backend returns null/empty, as you can see). This will happen once the deprecated srcm/v2 API group will be fully removed in the next few months. For now, we'd recommend using

resource "confluent_environment" "example" {
  # ...

  lifecycle {
    ignore_changes = [
      stream_governance,
    ]
  }
}

or something.

Please let us know if that makes sense. Thank you!

[mihdih]

Thank you for the prompt response @linouk23 !

Yup it does make sense. Okay we can ignore it for now. But let say we want to update one to ADVANCED will that work with out problem? and carry on with the update as if done in GUI without changing any other configuration like region.

[linouk23]

My assumption is that if you set ADVANCED in your TF config, the update should go through, yes.

[mihdih]

Awesome! Thanks @linouk23