fix: update threads chart tag

[casey-brooks]

Summary

• resolve threads image tag from chart version directly
• clear threads image tag override and bump chart version

Testing

• ./apply.sh -y

Issue

• Upgrade Argo CD Helm chart to latest (9.4.3) and set admin credentials via chart values #9

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y

[noa-lucent]

LGTM. Changes are minimal and correct:

• resolved_threads_image_tag now resolves directly to var.threads_chart_version (without v prefix), consistent with the new multi-arch release workflow in agynio/threads that tags images as 0.2.0 (not v0.2.0). This matches the pattern already used by gateway, k8s_runner, and chat.
• threads_image_tag override cleared to "" so the chart version drives the image tag.
• threads_chart_version bumped to 0.2.0.

Minor note: the PR body references #9 which resolves to #9 (ArgoCD upgrade), not the threads issue. The intended reference is likely agynio/threads#9. Not blocking.

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y
• terraform fmt -check -recursive

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[rowan-stein]

Requesting review. This PR updates the threads service deployment to use the new multi-arch release (v0.3.1):

• Removes format("v%s", ...) from threads image tag resolution — aligns with the semver tag convention from the new release workflow
• Bumps threads_chart_version to 0.3.1
• Clears the threads_image_tag override (derives from chart version)
• Converts Helm values from old custom chart format to service-base chart format (env list, service.ports)

CI (full-apply with k3d cluster) passes — threads pod is healthy.

[noa-lucent]

LGTM. All changes are correct and well-scoped:

• Image tag convention (main.tf:6): Drops format("v%s", ...) from resolved_threads_image_tag, now resolving directly to var.threads_chart_version. This aligns with the threads release workflow (PR agynio/threads#10) which tags images as 0.3.1 not v0.3.1 — consistent with gateway, k8s_runner, and chat.

• Helm values migration (main.tf:863-898): Converts from the old custom chart format (service.port, database.url, notifications.address) to the service-base chart format (service.ports list, env list). The structure matches the threads chart v0.3.1 values.yaml exactly. Also adds IDENTITY_ADDRESS and AUTHORIZATION_ADDRESS env vars required by the v0.2.0+ feature code.

• Version bump (variables.tf): threads_chart_version → 0.3.1, threads_image_tag override cleared to "" so chart version drives the tag.

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)

[casey-brooks]

Test & Lint Summary

• ./apply.sh -y (passed: 1, failed: 0, skipped: 0)
• terraform fmt -check -recursive (lint: no errors)