gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
kalbasit has joined #nixops
kalbasit has quit [Ping timeout: 265 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 265 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 256 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 244 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 246 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 272 seconds]
meh` has joined #nixops
meh` has quit [Remote host closed the connection]
lordcirth_ has quit [Ping timeout: 260 seconds]
cole-h has joined #nixops
lordcirth has joined #nixops
lordcirth_ has joined #nixops
lordcirth has quit [Ping timeout: 264 seconds]
lordcirth_ has quit [Quit: Leaving]
meh` has joined #nixops
meh` has quit [Ping timeout: 240 seconds]
<johnny101> adisbladis: We'd like to build nixops 2.0+plugins and have the binary available in lorri/direnv nix-shell without having to manually enter a `poetry shell` from that dir.
<johnny101> adisbladis: I see that question has been raised here also: https://github.com/nix-community/poetry2nix/issues/124
<{^_^}> nix-community/poetry2nix#124 (by takeda, 6 weeks ago, open): Make mkPoetryEnv include scripts.
<johnny101> adisbladis: I'm reading further for how to do this (and maybe I'll find an answer)
<johnny101> adisbladis: In the meantime, any pointers or docs to do this?
meh` has joined #nixops
meh` has quit [Ping timeout: 256 seconds]
kalbasit has joined #nixops
kalbasit has quit [Ping timeout: 264 seconds]
<johnny101> So, with a single plugin (ex: aws), I can use the plugin repo and modify the shell.nix file from mkPoetryEnv to mkPoetryApplication.
<johnny101> Which then makes the executable available in the shell. If I want to add additional plugins, looks like I can add additional poetry
<johnny101> deps to the other plugin repos in pyproject.toml, update the overrides file to include the new plugin deps, and generate a new lock file.
<johnny101> I've been able to get a nixops executable with aws + packet + nixos_modules_contrib this way.
<johnny101> But vbox and libvirt don't seem to play nice that way yet.
<johnny101> (and packet plugin doesn't appear to be functioning normally -- some work I've got to do there it seems).
<johnny101> I played around a little with trying to use the nixops core toml and lock file and add plugin deps to it, but couldn't get anything to work that way.
<johnny101> Could just be I'm not familiar enough yet. If we want to build nixops with multiple plugins, is there a recommended approach? Ex:
<johnny101> 1) Doesn't make much sense, but seems to work: start with a plugin repo and add more plugins to the toml and lock files
<johnny101> 2) Doesn't work for me so far, but would make more sense: start with the nixops core toml and lock files and add plugin deps to it
<johnny101> 3) Havent tried it yet, but maybe best: generate an independent toml and lock file which pulls in both core and plugin deps
<johnny101> Also, I'm making an assumption that we should be able to build as many plugins as we'd like into nixops. Is that assumption still valid with the new 2.0 poetry setup?
<adisbladis> johnny101: I suggest you take a look at https://github.com/NixOS/nixpkgs/pull/83548
<{^_^}> #83548 (by adisbladis, 18 weeks ago, open): nixops2Unstable: init at 2.0.0