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.
Copied PR body from #1202
As we are now using Flakes for development on master the scope of this PR is much smaller than the original one.
It's only about adding Flakes support to NixOps, we are not touching the development workflow.
This PR adds flake support to NixOps, meaning that you can do things like
This will create an EC2 instance running Hydra, using exactly the configuration locked by
flake.lock
.Currently evaluation is not as hermetic as we'd like since the NixOps-specific NixOS modules are provided impurely. Ideally, the flake would lock a particular version of the NixOps flake as input.
Likewise, NixOps needs to pass in the generated file
physical.nix
as an impure input. This is something of an inherent issue with the NixOps model. Maybe for flakes in local Git repositories,physical.nix
could be auto-committed.