deploy_nixos: parameterise concurrency controls of nix-copy-closure
#83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I often use this module to provision cloud machines that are incompatible with the host machine I am deploying from. In these cases, I often find that the slowest part is transferring
.drv
files to the remote machine, where they are then evaluated and built.This change exposes the
--max-jobs
parameter ofnix-copy-closure
to the terraform operator as a variable, so more than one derivation can be copied to the remote host at a time. This isn't officially documented in--help
/the man page ofnix-copy-closure
, but appears to be supported.In practice, this significantly improved my runtimes when deploying from incompatible host systems.