chore: migrate Helm provider to v3 in bootstrap roots#24
Merged
Conversation
Bump hashicorp/helm `~> 2.0` -> `~> 3.0` in both bootstrap roots
(cluster/local, cluster/scaleway) and adopt v3's typed nested-attribute
syntax:
- provider `helm` block: `kubernetes {}` -> `kubernetes = {}`
- `helm_release.argocd`: `set_sensitive {}` -> `set_sensitive = [{}]`
Re-locked both roots for darwin_arm64 + linux_amd64 (helm resolves to
3.2.0). Values are unchanged; `terraform plan` shows the ArgoCD releases
updated in-place (0 to destroy) — the metadata diff is the provider's
SDKv2 -> Plugin Framework state migration, not a recreate from the syntax
change. This also clears the false-positive terraform-ls warning
"Blocks of type kubernetes are not expected here".
Closes #23
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nbrieussel
marked this pull request as ready for review
June 11, 2026 13:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The two Terraform bootstrap roots (
cluster/local,cluster/scaleway) pinnedhashicorp/helmat~> 2.0and used its legacy v2 block syntax. Helm provider v3 rewrote the schema to typed nested attributes; the v2 syntax also triggers a false-positiveterraform-lswarning (Blocks of type "kubernetes" are not expected here). This migrates both roots to v3 with mechanical, value-preserving edits.Changes
Both roots (
cluster/local,cluster/scaleway):hashicorp/helm~> 2.0→~> 3.0inversion.tf(resolves to3.2.0).helmblock:kubernetes {}→kubernetes = {}(values unchanged).helm_release.argocd:set_sensitive {}→set_sensitive = [{}]..terraform.lock.hclfordarwin_arm64+linux_amd64viamise run lock.Untouched:
state-backend,github-ci; no chart/version/values change; noregistry/experiments/set/set_listmigration (unused here).Verification (plan-only, no apply)
terraform fmt+validate: clean in both roots.cluster/local plan(against minikube): 0 to add, 2 to change, 0 to destroy — ArgoCD releases updated in-place. Themetadata → known after applydiff is the provider's SDKv2 → Plugin Framework state migration, not a recreate from the syntax change.cluster/scaleway plan -var bootstrap_argocd=false: succeeds with ArgoCD gated off; no helm errors.helm 3.2.0with hashes for both platforms.Closes #23
🤖 Generated with Claude Code