Yes I see. While I can't prove it at the moment, I think skipping the types loses us a valuable opportunity to generate rich documentation for application authors and hosting providers. And that…
proxmox-*.sh scripts
What about the failing tests. @kiara I remember dimly we discussed it somewhere.
The small changes dotting the i-s make sense, thanks a lot! The larger one not so much.
Very likely not needed, as noted in the other PR
I don't think this is an improvement in readability
I'm not even sure this is needed at all, the import should give us that anyway
Thanks!
ah that. but that's just a data structure you can convert to any deployment method.
hmm i'd say it's more about practicality. will application authors be able to work fluently with an interface that doesn't force type checks on them?
Tip: Do both. Put stuff that belongs together into nested attributes for readability, and flatten them in flake.nix so it fits the required form.
makeResourceModule
Not sure. Depends on how much you want the directory structure to play a semantic role.
yes I left it to keep some intermediate diff small, will fix up...
yes, this is why I left the TODO to consider transposing the resource attrsOf, so we could pass just the request(s) for that same resource to this function. we supposedly wouldn't (want to) care…
I'm not sure I get the question. Yes, the mapping deals with the specific instance of a policy, as one can (hopefully) observe in the test, where we set the username to "operator".