gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
cole-h has quit [Ping timeout: 246 seconds]
stoile has quit [Ping timeout: 264 seconds]
stoile has joined #nixops
jkachmar has quit [Quit: Connection closed for inactivity]
cole-h has joined #nixops
cole-h has quit [Ping timeout: 272 seconds]
hmpffff has joined #nixops
nextloop has joined #nixops
jD91mZM2 has quit [Quit: ZNC 1.8.1 - https://znc.in]
jD91mZM2 has joined #nixops
adisbladis has joined #nixops
teto has joined #nixops
meh` has joined #nixops
deadk has quit [Quit: edk]
deadk has joined #nixops
cole-h has joined #nixops
hmpffff has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hplar has quit [Ping timeout: 256 seconds]
hmpffff has joined #nixops
hplar has joined #nixops
meh` has quit [Ping timeout: 256 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 246 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 246 seconds]
hmpffff has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<lukebfox[m]> risson: if you use defaults._module.args at the top level you can add arguments to modules declared in any machine's imports definition if this helps, but you can't provide different arguments to different machines this way, so it has limitations.
<lukebfox[m]> i use it in flakes which export a nixops network so I can reuse nixosModules output in both nixosConfigurations and nixopsConfigurations output, where my modules tend to take a utils argument and shared/secrets args
<lukebfox[m]> i would love to know if there is a way to somehow use a nixosConfiguration config artifact for specifying the logical part of a machine in the nixopsConfiguration output
deadk has quit [Quit: edk]