Development overrides for providers under development

Terraform
5

Interesting, I brute forced my way around this problem with a simple make target

tf: install
	rm -f examples/sequence_file/.terraform.lock.hcl
	terraform -chdir=examples/sequence_file init
	terraform -chdir=examples/sequence_file plan

Avoiding the init would speed up the iteration time though.

Based on just reading your comment and the linked documentation (I’ll try and find time to give it a try over the weekend) my concern with with the CLI configuration solution is that there is a risk of mistakes if not very careful when context switching between working on a provider and using terraform for practical work. For example;

  1. Configure CLI to use my local build
  2. Do some work creating a PR against existing provider
  3. Pager goes off/colleage/dev asks for assistance
  4. Run terraform against a real project
  5. ooops did I just use my local provider instead of the stable one?

I think I would feel safer if there was just some kind of no_lock parameter in the required_providers block, then I could turn off the lock for a simple test and maintain my safety for the day to day operations work.