5 ms·
Very excited to see this (if it is what I think it is...). Still reading about it. I really like Terraform but haven't been a fan of the existing way of bringi
by atonse 9y ago
Very excited to see this (if it is what I think it is...). Still reading about it.
I really like Terraform but haven't been a fan of the existing way of bringing external code into my terraform scripts, via some strange go-like "refer to this github" repo mechanism.
Hopefully this makes them package able artifacts. Looking forward to watching the keynote and other videos from Hashiconf.
- jfroma 9y agoI'd really love to be able to build modules in some other language like python, ruby or even javascript just because I am not very fluent yet in Go and its tooling.
- charlieegan3 9y agoThe modules are written in HashiCorp configuration language.
- lmickh 9y agoYou can use json as well, but it is pretty unfriendly for the human users and you lose some of the interpolation.
- meddlepal 9y agoHowever, very useful if you're code generating Terraform config because there are not a lot of HCL serializer/deserializer libs in existence.
- jfroma 9y agoYou are right, I should have say "providers" with new "resources" and yes, this new registry is for modules, not providers.
- jen20 9y agoIf you want to build custom Terraform providers _without_ using Go, this is actually on the cards now: as of `hashicorp/go-plugin#fa4a2a351`, plugins can use gRPC to communicate with the core of Terraform. I don't know if anyone has implemented the primitives for building providers in another language, but it's now possible without too much pain. [1]: https://github.com/hashicorp/go-plugin/commit/fa4a2a351f33b106d320ffadd69184504e040384 https://github.com/hashicorp/go-plugin/commit/fa4a2a351f33b1...