hi there!
i noticed the implementations here seem maybe a bit verbose to the point of manually wrapping much of the upstream TF providers, making me wonder if perhaps more of that could already be inferred from the TF providers themselves.
this should hopefully limit maintenance surface, while making it easier to keep the code up to date as the TF providers publish updates.
if it helps, both nixops4 as well as fediversity have done stuff around such reflection-based generation of nix modules from TF resources before.
hi there!
i noticed the implementations here seem maybe a bit verbose to the point of manually wrapping much of the upstream TF providers, making me wonder if perhaps more of that could already be inferred from the TF providers themselves.
this should hopefully limit maintenance surface, while making it easier to keep the code up to date as the TF providers publish updates.
if it helps, both nixops4 as well as fediversity have done stuff around such reflection-based generation of nix modules from TF resources before.