feat: expose --generate-hardware-config nixos-facter thru TF

[KiaraGrouwstra]

add var.nixos_facter_path to TF modules install / all-in-one.

c.f. #407, which handled --generate-hardware-config nixos-generate-config.

P.S.: this PR builds upon that one, figuring it would be more elegant to use the elif than have two separate if statements.

[Mic92]

We don't have a integration test for terraform. @KiaraGrouwstra could you test this one more time to make sure nothing is broken. Otherwise I would need to run a test later.

[KiaraGrouwstra]

@Mic92

We don't have a integration test for terraform. @KiaraGrouwstra could you test this one more time to make sure nothing is broken. Otherwise I would need to run a test later.

tho in retrospect separate from TF, i pushed an update to the nixos-anywhere bash script to ensure any directories of hardware configuration files would be created, if needed.

that made it a bit more robust, and had it go thru for me. as in #407, in my use i am still checking if pathExists again using (lib.optionalAttrs (lib.pathExists reportPath) { config.facter = { inherit reportPath; }; }). that is, if using flakes + git, the user is currently still expected to manually stage the generated file to git for the nixos config to actually pick it up.
(that said, that particular weakness too i think seems not specific to TF.)

[Mic92]

The git add we already do:

nixos-anywhere/src/nixos-anywhere.sh

Line 458 in 3fb834d

git add --intent-to-add --force -- "$hardwareConfigPath" >/dev/null 2>&1 || true

[Mic92]

@mergify queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 51d347d