-
Notifications
You must be signed in to change notification settings - Fork 376
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
data helm_repository requires helm repo update #438
Comments
+1 also seeing this issue |
+1 also seeing this as well |
I kinda work around by appending uuid after the name value of helm_repository, but the side effect is it get updated every time. |
I suspect this is the same issue as #416 |
Replacing |
I'm ditching the
|
Thanks for the hint! If version is missing:
The root of the issue seems to be:
Doing so will lead to the error:
So the requirement to checkout the chart is part of the |
We're running into this issue as well. We have exactly a setup as @timmjd describes: In our case we're running GitLab. We have a plan and an apply ci job and they both run in Docker containers. The plan job generates the plan which is then passed as an artifact to the apply job. Then, the apply job fails applying it with an error like above. |
When installing external-dns, it doesn't do helm update: Error: failed to download "bitnami/external-dns" (hint: running `helm repo update` may help) See: hashicorp/terraform-provider-helm#438 Using the .url instead of .name (and therefore changing the chart name too) fixes it.
When installing external-dns, it doesn't do helm update: Error: failed to download "bitnami/external-dns" (hint: running `helm repo update` may help) See: hashicorp/terraform-provider-helm#438 Using the .url instead of .name (and therefore changing the chart name too) fixes it.
When installing external-dns, it doesn't do helm update: Error: failed to download "bitnami/external-dns" (hint: running `helm repo update` may help) See: hashicorp/terraform-provider-helm#438 Using the .url instead of .name (and therefore changing the chart name too) fixes it.
As a workaround I defined URL to chart in the chart field like that:
Everything works fine. However I use terraform-0.12.24. Hope it helps. |
Note that in #466 the helm_repository data source has been deprecated, with the new recommended way is putting the repo URL directly in as the "repository" field of the helm_release. |
With the docs now clearly saying that the repo data source is deprecated and the example on the helm_release page updated without it, I think this issue can be closed. |
sounds good to me, will close this issue. |
Posting this in case someone else lands here looking for answers. I was still having issues after removing the data source and converting to using the repo url in the "repository" field. Example:
would yield:
I ended up clearing out my helm cache which resolved the issue. Apparently if you've installed the chart prior to converting, there are some remnants left that cause issues. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Terraform Version
Terraform v0.12.23
Affected Resource(s)
helm_repository
Terraform Configuration Files
Debug Output
Expected Behavior
helm_repository data resource should help download required charts
Actual Behavior
The corresponding
terrafoom apply
on Terraform cloud showed the above error message asking to runhelm repo update
The text was updated successfully, but these errors were encountered: