-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Terraform: Support lockfile generation for community providers #10550
Comments
Thank you for providing a reproduction! 🎉 🚀 The Renovate team will take a look at the reproduction repository. |
I think your issue is the name casing. you are using |
I will evaluate, however the provider's name is actually a uppercase |
OK, confirmed, only official providers are supported renovate/lib/manager/terraform/lockfile/hash.ts Lines 120 to 124 in eb8ad0c
@hojerst Please replace the bug template with a feature request template |
It doesn't work with |
I changed the description to a feature request as requested. |
🎉 This issue has been resolved in version 25.63.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What would you like Renovate to be able to do?
Terraform currently supports an experimental feature for generation of terraform lockfiles. However, this only works for providers which are provided by hashicorp. When using community providers, the lockfile is not updated for those. This essentially invalidates the lockfile for community providers. The feature usability would be increased when it also supports community providers.
Did you already have any implementation ideas?
Disclaimer: I don't know the details of the terraform provider hosting, nor am I a expert for the renovate internals, so take the following with a grain of salt.
lib/renovate/managers/terraform/lockfile/*
could be extended to fetch community zip's from the github.com releases for the respective providers.The text was updated successfully, but these errors were encountered: