Martin Atkins

Hi @wyardley! Can you say a little more about how you are using Renovate? I ask because my understanding of Renovate is that its purpose is to automatically propose upgrading...

I guess my ideal model of how Renovate should behave with Terraform is to _only_ update the lock file, and to propose selecting the highest-precedence provider version (per semver rules)...

I suppose where I'm getting caught up with this discussion is that we added the lock file specifically because people found it annoying that the version constraints in the configuration...

Thanks for sharing these examples, @wyardley! One specific potential improvement I can see from what you've shared is in how `terraform init` deals with a situation where the lock file...

Separately, it also seems like Renovate is running into hashicorp/terraform#27161 and with the new context here, I can see that it was opened directly in response to Renovate's challenges using...

Hi @wyardley, Thanks for sharing those examples. I see what you are getting at now. In your most recent example I see that you found the `lock.json` file I was...

Hi @secustor! Thanks for sharing that extra context. For the backend credentials issue at least, I'd suggest trying `terraform init -upgrade -backend=false`, where `-backend=false` instructs Terraform to _not_ initialize the...

Hi @ohookins, If you intend to lock the checksums in your local mirror directory, instead of the ones in the origin registry for each provider, then you can use the...

Hi @nwmcsween! Thanks for sharing this feature request. The major design question that needs to be answered to move forward with a design like this is: Backend initialization currently happens...

Hi all! I think there are at least four remaining design questions to be solved before something like this could be implemented: * The usual reason given to motivate this...