New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable nix
as _config_ language
#619
Comments
Or the other way round: a jsonschema to nixpkgs module system converter? 😄 (for eval time validation without IFD) Adios terranix, kubenix, etc. |
Actually, thinking of it a bit more, the best option would be: |
I like the idea, as writting complex terraform modules in hcl has been a pain many times, Nix allows for more intuitive constructs, functions, etc The implementation of this I think would be modules like terraformTest accepting both src OR (not both) asTerraformHcl is an argument that dumps nix-lang to json and perform terraform-hcl schema validation A point to take into account is that keeping compatibility with what people find in tutorials on the internet is important anyway, as for organizations like us migrating 14000 lines of code of HCL to Nix is not easy, fast nor cost-efficient. And for new-comers of Makes having to change so drastically can be daunting. I think it is better to offer both worlds, so we flirt with them slowly, allowing them to see the Nix benefits early and at their own pace, until they fall in love like we both did |
I've run the idea of I think the general stance is: if that doesn't entail huge deps for But realistically, I see that some consensus might be possible on this. |
x-posting from matrix discussion, since I started breeding over this yesterday:
|
I might have cracked the classical array merge problematic in a very lightweight way that can work with arbitrary left-hand-side data structures (eg. coming from json or hcl). https://gist.github.com/blaggacao/050483417bcab6a5cd126152b0187314 |
This is coming from thinking about nomad & terraform deployments.
In my thinking, we could bring the power of
nix-lang
to those tools by:Let me know what you think of this generic approach to use
nix
as the configuration language wherever json schemata are published...The text was updated successfully, but these errors were encountered: