Always change?

[fabricesemti80]

Ask a Question!

Hi.

I have these files, as I try this provider out:

infra-terraform-home-portainer on  main [!] on ☁️  emilfabrice@gmail.com 
❯ cat ./terraform/services.tf                                                                     

## Tailscale stack

resource "portainer_stack" "tailscale" {
  name               = "tailscale"
  endpoint_id        = 3
  stack_file_path = "../services/tailscale/docker-compose-tailscale.yml"

  method            = "file"
  deployment_type   = "standalone"

  env {
    name  = "TS_AUTHKEY"
    value = var.ts_auth_key
  }


}
infra-terraform-home-portainer on  main [!] on ☁️  emilfabrice@gmail.com 
❯ cat services/tailscale/docker-compose-tailscale.yml
services:
  tailscale:
    image: tailscale/tailscale:latest
    container_name: tailscale
    restart: unless-stopped
    volumes:
      - /srv/docker-appdata/tailscale:/var/lib/tailscale
    networks:
      - srv-net
    cap_add:
      - NET_ADMIN
      - NET_RAW
    environment:
      - TS_AUTHKEY=${TS_AUTHKEY}
      - TS_EXTRA_ARGS=--advertise-routes=10.0.40.0/24 --accept-routes

volumes:
  tailscale_data:
    driver: local

networks:
  srv-net:
    driver: bridge

The deployment is succesfull, but at each subsequent run I see a change:

terraform-apply] $ cd terraform && terraform plan --out=tfplan && terraform apply --auto-approve t…
portainer_tag.test_tag: Refreshing state... [id=1]
portainer_stack.tailscale: Refreshing state... [id=3]
portainer_endpoint_group.test_group: Refreshing state... [id=2]
portainer_environment.qnap_agent: Refreshing state... [id=8]
portainer_environment.media_vm: Refreshing state... [id=9]

Terraform used the selected providers to generate the following execution plan. Resource actions
are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # portainer_stack.tailscale will be updated in-place
  ~ resource "portainer_stack" "tailscale" {
        id                            = "3"
        name                          = "tailscale"
      - stack_file_content            = <<-EOT
            services:
              tailscale:
                image: tailscale/tailscale:latest
                container_name: tailscale
                restart: unless-stopped
                volumes:
                  - /srv/docker-appdata/tailscale:/var/lib/tailscale
                networks:
                  - srv-net
                cap_add:
                  - NET_ADMIN
                  - NET_RAW
                environment:
                  - TS_AUTHKEY=${TS_AUTHKEY}
                  - TS_EXTRA_ARGS=--advertise-routes=10.0.40.0/24 --accept-routes
            
            volumes:
              tailscale_data:
                driver: local
            
            networks:
              srv-net:
                driver: bridge
        EOT -> null
        # (15 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

───────────────────────────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"
portainer_stack.tailscale: Modifying... [id=3]
portainer_stack.tailscale: Modifications complete after 0s [id=3]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Is this normal? (For sure I could use lifecycle to ignore the change of contents, or in-line string, but none of them is desirable...

[grulicht]

Hi @fabricesemti80 ,
thanks a lot for using the Portainer Terraform provider and for taking the time to report this issue – your detailed reproduction and example repo are super helpful! 🙌

We're investigating the root cause and will include a fix in one of the upcoming releases. We'll make sure to notify you once it's available. 🚀

[grulicht]

Hi @fabricesemti80 ,
New release version v1.13.1 with patch is out! 🙌🏽