coretemp

@betaboon Your suggestion ("you could always do") fails with `The option networking.privateIPv4 is used but not defined.`.

@betaboon Thanks for you reply. As you can see, I am not passing `--build-only`: `nixops deploy -s localstate.nixops --kill-obsolete -d foo --allow-reboot --show-trace`

Any description of `my_machine` would do (I expect even an empty one), so just pick the one from the NixOps manual or one of your own. I think the easiest...

`master`

This is the same issue, but for Hetzner. https://github.com/NixOS/nixops/issues/707

`nixops info` shows: ``` fooResource | Starting / Obsolete | ec2-security-group [eu-west-1] | fooResourceNix | | ``` I don't really see how an ec2-security-group can be in "Starting" mode. Something...

Has this ever been implemented? vpc.nix seems to contain at least part of this, but I haven't figured out yet how to build an HTML manual for a recent version...

This issue is blocked by https://github.com/NixOS/nixops/issues/504.

@danbst I will believe that it works when I see a test in the nixops repository doing exactly what I described, because I have tried these things and it does...

@AmineChikhaoui Yes, this is about non-machine resources. ``` # this is the network configuration (as per NixOps manual) {arguments}: let machine1 = ; machine2 = ; in { ; resources.ec2SecurityGroups.mysecuritygroup...