Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

octopusdeploy_tenant re-orders tenant_tags #845

Open
itaispiegel opened this issue Dec 24, 2024 · 0 comments
Open

octopusdeploy_tenant re-orders tenant_tags #845

itaispiegel opened this issue Dec 24, 2024 · 0 comments

Comments

@itaispiegel
Copy link
Contributor

Describe the bug
the resource octopusdeploy_tenant always plans to re-order the tenant_tags, even though they are a set and should ignore the ordering.

Steps to reproduce

  1. Define a resource such as:
resource "octopusdeploy_tenant" "tenant" {
  name = "my-tenant"
  tenant_tags = [
    var.environment == "prod" ? "Env/Prod" : "Env/NonProd",
    "Env type/Cloud",
    "Cloud Type/A"
  ]
  1. Plan and apply it.
  2. Plan again, and expect to see the following output:
Terraform will perform the following actions:

  #octopusdeploy_tenant.tenant will be updated in-place
~ resource "octopusdeploy_tenant" "tenant" {
        id                    = "Tenants-724"
        name                  = "my-tenant"
      ~ tenant_tags           = [
          - "Env/Prod",
            "Env type/Cloud",
            "Cloud Type/A",
          + "Env/Prod",
        ]
        # (1 unchanged attribute hidden)
    }

Expected behavior
Terraform should completely ignore the ordering of tenant_tags as it's a set.

Environment and versions:

  • Octopus Server Version: `v2025.1 (Build 2648).
  • Terraform Version: v1.8.5.
  • Octopus Terraform Provider Version: `v0.12.5.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant