gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
nuncanada has quit [Ping timeout: 246 seconds]
nuncanada has joined #nixops
nuncanada has quit [Read error: Connection reset by peer]
nuncanada has joined #nixops
nuncanada has quit [Client Quit]
virus_dave has quit [Read error: Connection reset by peer]
virus_dave has joined #nixops
cole-h has quit [Quit: Goodbye]
raghavsood has joined #nixops
<raghavsood> Is there any way to iterate the full node list for an entire network in nixops? I have 6-7 nodes, all on hetzner, and I'd like to whitelist all of their IPs for a given port on each node
<raghavsood> Is there a way to iterate `nodes.<name>.config.networking`? I usually only deploy to a single machine via `--include`, so would iterating that trigger full machine builds for the others?
<raghavsood> Or would it use the most recent physical machine config?
<gchristensen> it would fully evaluate but not build
<raghavsood> That should be fine, I actually usually deploy to one machine so I can save time on copying closures to machines where nothing has changed
<gchristensen> so yeah go ahead and iterate over nodes
<raghavsood> Thanks for the sanity check!
<gchristensen> yep!
<raghavsood> So, potentially dumb follow up question - how do I actually iterate it? I've got https://gist.github.com/RaghavSood/e3b3287bacd078aa8720f4f021d59ad0, but it throws `value is a set while a list was expected`
<raghavsood> Tried searching github, but not much nixops stuff out there to use as examples
<raghavsood> Ah, I might have gotten it
<raghavsood> This seems to work, happy to hear suggestions! https://gist.github.com/RaghavSood/bc440ca547fab044603d9ca3408d4504
<raghavsood> How would I make nixops use unstable packages? I tried adding the unstable channel as `nixpkgs` for my deployment machine (under the same user that executes nixops deploy), but it doesn't seem to pick up unstable channels still
<b42> run nixops create/modify with -I nixpkgs=channel:nixos-unstable maybe?
<raghavsood> Well, it does seem to be downloading a system's worth of packages now, so that might have worked
<raghavsood> Interestingly, the nix.nixPath option given here (https://github.com/NixOS/nixops/issues/736) didn't work for me - it accepted it, but didn't actually update anything
<{^_^}> nixops#736 (by bobvanderlinden, 2 years ago, open): nixops depends on nix-channel
<gchristensen> "You can set nix.nixPath in your nixops logical configuration for each machine." should update the Nix channel *on the machine* but not the nixpkgs used to build the system
<raghavsood> Fair, perhaps I should set up one of the machines as a build slave and use that route before this poor laptop runs out of space
<gchristensen> in other words, nix.nixPath takes effect after the deploy
meh` has quit [Ping timeout: 246 seconds]
cole-h has joined #nixops
pistache has quit [Ping timeout: 260 seconds]
pistache has joined #nixops
meh` has joined #nixops
meh` has quit [Ping timeout: 260 seconds]
dongcarl has quit [Read error: Connection reset by peer]
meh` has joined #nixops
virus_dave has quit [Quit: virus_dave]
pbb has quit [Remote host closed the connection]
pbb has joined #nixops
virus_dave has joined #nixops
meh` has quit [Ping timeout: 260 seconds]