programs/nh: allow flake uris to be set

[Shawn8901]

This allows a configuration like

  programs.nh = {
    enable = true;
    flake = "github:shawn8901/nix-configuration";
  };

which lets the user use nh module even when the flake is not available locally (nh itself supports that anyways already).

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[JohnRTitor]

I think we should provide an example here.

[Shawn8901]

Whoms config should I add, or build up an crafted dummy? I was also thinking about that as the Auto-Upgrade provides one, but I didn't want to copy the example nor I wanted to artificially promote my own repos. I mean if all a fine with that, I can do so.

Or do we have any other reasonable?

[Shawn8901]

@JohnRTitor i rephrased the description to include examples how a flake reference that can be passed looks like. As i wanted to provide an example for both i opted against using the example field. Let me please know if i should fill that with one of the options.

I used crafted dummy paths.

[viperML]

@Shawn8901 In any case, NH 4.0 will support any installable (-f, --expr, etc) and I want to support multiple env variables. So we will probably have to rework the module in any case.

[Shawn8901]

Honestly i am not sure if i misunderstand the intention of the comment (or am just super salty at the time reading the response). Unless there is a planned release date for that reworked 4.0 version within the next days, wouldn't it be more okayish to just improve the UX on the old state?

But it sounds for me, that we are preferring to wait for some rework in the future.
For me sad, as it kind of just started about arguing about how a flake reference might look like and give examples about it (but those should be hopefully known anyways, when using flakes, as they are used on every ones input attrs).

But i am fine in not doing it and just pick that change to my own fork until there is some rework available.

[viperML]

I already approved the PR, just wanted to add that remark

[JohnRTitor]

For me sad, as it kind of just started about arguing about how a flake reference might look like and give examples about it

I came here to merge this you know. There was no need to close this PR.

[sjdrc]

Ran into this issue just now. Can we re-open this? Or shall I open a new MR?

[JohnRTitor]

Reopening this isn't possible as the OP deleted their branch, just cherry-pick the commits

[Shawn8901]

Ran into this issue just now. Can we re-open this? Or shall I open a new MR?

Feel free to open as a new PR