nixos/restic-rest-server: prometheusNoAuth flag

[oxzi]

Description of changes

Expose the --prometheus-no-auth flag to the module.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 22.05 Release Notes (or backporting 21.11 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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[dotlambda]

I think extraFlags is good enough.

[bachp]

I think extraFlags is good enough.

@dotlambda Is there a recommendation when to expose as a module option vs requiering the use of extraFlags?

[oxzi]

I think extraFlags is good enough.

Wouldn't this be true for like every flag? Imho, this results in an ugly mixed configuration between "nixified" options and a list of extraFlags. I'd second @bachp's question when which should be used.

[dotlambda]

The proper solution would be following NixOS/rfcs#42 but that seems a little hard in the case of command line flags.
We could have an option flags that replaces all existing options and translate e.g.

flags = {
  path = "/foo/bar";
  tls = true;
};

to --path "/foo/bar" --tls.