151–160 of 392 posts
Terraform is terrible as it is. Good riddance. We need real tools instead of messing around with text files with ridiculous formatting.
Earlier quoted context omitted.
The worst part is they did create a viable business model. They were profitable when they had their IPO. They then pretended that the IPO was just another Series X investment, blew all the money, and went negative on their cashflow. Hashicorps problem isn't that their business model doesn't work, it's that they are really bad at their jobs. They ignore customer feedback, laid off support people, and then jacked their…
Have you actually read the financial statements? None of what you just wrote is remotely true.
Terraform core is kinda crappy. The language is awful, and the module infrastructure sucks. I would support (with my own money) a fork that would re-use the Terraform providers, and reimplement the language as something not so insane.
I am working in VSCode, which by and large tends to be the editor supported best, with the most mindshare. Terraform has static and mostly strong typing, yet some testing revealed I was able to pass an argument of the wrong type to some variable I declared. This is type safety 101: variable declared `str` shouldn't accept `int`, ever. Yet `tf validate` was silent, so was all IDE-integrated tooling (whatever the VSCode TF extension does).
Jumping to/from symbol definitions/usages was also flaky (but not entirely absent).
Really disappointing! My excitement of diving into TF went poof. Maybe I'm overly sensitive, but I was so excited to escape YAML hell (Ansible).
Now I'm even firmer in the boat of just using a regular old language, like Pulumi with Python (with full typing).
Did I do something wrong or can anyone confirm my findings?
Terraform is terrible as it is. Good riddance. We need real tools instead of messing around with text files with ridiculous formatting.
1. IaC description should be format agnostic and transformable (eg definable in yaml, json, whatever).
2. Something about provider interfaces here, but it's already super messy and not sure if it's an improvement or just a shift
3. State files were wild west last time I checked. And there should be a default database interface provider at minimum. Maybe there is now?
4. Forcing the apply->statefile cycle as the default requires all of compute, interface, and a human. This should have been an abstraction on a raw interface for automated use.
Earlier quoted context omitted.
It isn’t a miscommunication, jen20 is astroturfing for hashicorp. Look at all of their recent posts.
"Astroturfing"... lol OK. I don't think I've ever made it a secret that I worked for HashiCorp in the early days (leaving in 2017), and have been critical to the point of being banned by the CEO from speaking at HashiConf. Saying "Terraform doesn't have a test suite" is not miscommunication, it is misinformation, plain and simple - the same as most of the other things I have been correcting this week (not least from…
Earlier quoted context omitted.
You can continue to use plain Terraform forever. It would only affect you if you use a tool like Env0, spacelift, Gruntwork pipelines, etc instead of something like the Terraform Cloud. These tools are not going to be able to be used with users using new Terraform versions (though they can always use the current or any previous versions, or can use their fork these companies are jointly supporting). Then there are op…
> These tools are not going to be able to be used with users using new Terraform versions As discussed in the other thread, we believe that we are not in violation of the new license, you can find more details in our today's announcement[0]. Disclaimer: Work at Spacelift. [0]: https://spacelift.io/blog/spacelift-latest-statement-on-hash...
Best of luck with Spacelift :)
As a regular end-user of Terraform, what difference does BSL vs MPL make to me? From reading this article it seems not very much? Perhaps I'm misreading this.
Earlier quoted context omitted.
> These tools are not going to be able to be used with users using new Terraform versions As discussed in the other thread, we believe that we are not in violation of the new license, you can find more details in our today's announcement[0]. Disclaimer: Work at Spacelift. [0]: https://spacelift.io/blog/spacelift-latest-statement-on-hash...
Oh neat, thanks for sharing this! I had read https://spacelift.io/blog/hashicorps-license-change last week, but hadn't seen this blog yet. Best of luck with Spacelift :)
Earlier quoted context omitted.
Smells like the end of Chef. Management doesn't understand how much it takes to maintain the open source project and is just pouring resources into sales and marketing and products that they can charge for, and don't see how that erodes goodwill and the technological foundation of the company.
I also saw that parallel with Chef. I think its the story of all VC funded software that attempts to be "Open Source". For them, Open Source means "You can read the source code, and potentially fix a bug", for us, it means community, transparency, and fixing bugs beyond those your paying customer has. I looked at github /chef/chef and github /inspec/inspec and its the same as it was shortly after I left. The only cha…
It's all good and "fun" on the IPO up.
(in x months we will rewrite the whole universe).