2 ms·

I use Nix for that all of the time. My workflow is usually like this: * upstream has a bug. * find and fix the bug, send a PR. * update the Nix code to build w

I use Nix for that all of the time. My workflow is usually like this: * upstream has a bug. * find and fix the bug, send a PR. * update the Nix code to build with either the PR branch as the source, or the PR diff as a patch. What's missing is a good tool to scan for new releases and remove the override. Other than that it works really well. It's much nicer to run a terraform provider from a branch than having to publish a temporary fork to registry.terraform.io

arianvanp 5y ago
I spent my last week wasting hours on end how i could ship a fork of the aws provider to support some resources that upstream refuses to add (ec2 classic link). Wasted hours on end convincing terraform not to redownload or to not have hash collisions with their built in way to do this so i indeed ended up using nix to patch and ship the terraform provider in the end! Very nice experience. My edits are purely additive so I have it as a patch file that I simply apply to the nix package definition. So far it has applied cleanly on many different terraform versions I use in the wild.