Robert Hensing

I think maybe we should default `-d` to the attribute name as well, although storing multiple deployments in the same remote state is a bad idea because of locking.

You can achieve this with type-merging, although a more obvious solution would be nice. Something like this _should_ work: ``` # nixops network defaults. You could do it for a...

This needs documentation and tests. We have unit tests in tests.py and the tests directory, or https://github.com/NixOS/nixpkgs/pull/142035 could be added here for end to end tests. Not sure if eval-machine-info...

This could be split up into two changes, one to define the whole network via the module system, the other to add a resource similar to `commandOutput`, but which doesn't...

This issue is mostly about getting secrets out of Vault at deployment time, whereas `nixops-vault` currently only supports the creation of resources inside vault; writing to vault. I suppose it...

That said, (1) is probably not what you want anyway. Vault Agent [templating](https://www.vaultproject.io/docs/agent/template) would be preferable in most setups.

Which commit of NixOps are you using? This seems to be a regression of #1435 if it's recent.

Will consider after #1508

We should require a `system` string for all nodes. We can only assume the default to be wrong. Probably implementable with an `assertions` on `options.nixpkgs.system.highestPrio`? Unsetting the default in nixpkgs...

This appears to be a Nix issue. Nix has behavior that disables caches when they're down now. It may [not](https://github.com/NixOS/nix/issues/3796) be perfect yet though.