Live data from Hacker News

The OpenTF Manifesto

opentf.org

241–250 of 392 posts

Re: The OpenTF Manifesto

#241
post #102

Earlier quoted context omitted.

Just went with Elastic cloud after evaluating both Elasticsearch and OpenSearch. It was an easy choice to stick with the incumbent/creator that I was familiar with. No complaints so far.

We just went back to TF after giving Pulumi a try. Prefer declarative syntax for infra and more abuse of Yaml ("fn::..." here) is not what I'm after. We are working on wrapping TF in CUE since you can CUE->JSON->TF https://github.com/hofstadter-io/cuelm Many more CUE experiments are going on in the devops space

Pulumi has a few languages other than YAML and Pulumi is declarative[1], and the programs you write are only as complex as you want them to be. This python program declares an S3 bucket and declares ten objects to exist in it.

    from pulumi_aws import s3

    bucket = s3.Bucket('bucket')

    for i in range(10):
        s3.BucketObject(
            f'object-{i}',
            s3.BucketObjectArgs(
                bucket=bucket.id,
                key=str(i),
            )
        )

Even so, Pulumi YAML has a "compiler" option, so if you want to write CUE or jsonnet[1], or other[2] languages, it definitely supports that.

Disclaimer: I led the YAML project and added the compiler feature at the request of some folks internally looking for CUE support :)

[1] https://www.pulumi.com/blog/pulumi-is-imperative-declarative...

[2] https://www.pulumi.com/blog/extending-pulumi-languages-with-...

[3] https://leebriggs.co.uk/blog/2022/05/04/deploying-kubernetes...

Re: The OpenTF Manifesto

#242

Earlier quoted context omitted.

Marcin here, co-founder of Spacelift. Even though I strongly believe the OpenTF fork could open up incredible possibilities for the community (I could go on and on about it), it is an equivalent of a civil war. It doesn't serve the community and our only interest is in the continued strength of the community that we continue to build for. Based on my immense respect for what's been built under Hashi's umbrella I'd ra…

> it is an equivalent of a civil war. Why. It is open source. A fork should be no big deal, and definitely not a “civil war”. I think the community should be quicker to fork open source projects that are not serving the needs of the community. The corporations are trying to have the benefits of open source without the responsibility. Forking is a normal, acceptable part of open source and we should normalize it.

What would it mean to “normalise” forking? The costs of maintaining a fork are significant, and if one group of programmers are being funded to work on the project then it can be very difficult to fork a project in any meaningful way without significant resources behind it.

Also IIUC most of the parties in this conversation are corporations. They’re all trying to enjoy the benefits of open source development for a variety of reasons.

Re: The OpenTF Manifesto

#243

Earlier quoted context omitted.

What? Docker is still completely open source apart from the desktop GUI. The engine and (I'm pretty sure) all components are completely free and if anything, they have pushed for the standardization of the container runtime. Buildkit is free, compose is free, no feature is paywalled apart from Mirantis-centric stuff (not part of docker inc) You can absolutely bet that they would get dropped like a rock if they moved…

Didn't Docker actually try it earlier this year, e.g., https://blog.alexellis.io/docker-is-deleting-open-source-ima... ?

That's just hosting though iirc. Docker hub is very important, but it's not really part of Docker the software. As in, you could deploy your own container registry with 0 licensing issues. They just didn't want to pay the bandwidth costs anymore, though I think they walked back on that for open source images.

Re: The OpenTF Manifesto

#244

If any Hashicorp people are reading, can you please tell your middle and senior management that this decision has deeply soured my entire DevOps cohort on continuing to use Terraform in the future. We're already exploring alternatives. Future client projects may not use Terraform at all. Languages and frameworks must remain open or they will wither and die.

> Languages and frameworks must remain open or they will wither and die. Terraform is neither a language nor a framework, and I certainly don't think it will wither and die if they transition to BSL. Case in point, docker's revenue grew by 12x once they started taking control of their code and stopped caring about community. Same with postman or nginx or many other companies.

Nginx is FreeBSD License, The Docker Engine is licensed under the Apache License 2.0

Re: The OpenTF Manifesto

#245

I appreciate the letter and trying to work with Hashicorp -- I used to have a ton of respect for Hashicorp. But honestly... at this point... ...just fork it into a foundation. Don't wait for Hashicorp's response. I get wanting to have the appearance of working with Hashicorp, but we've been shown again, and again, and again, and a-fucking-gain that private corporations cannot be trusted to maintain public goods. Only…

Marcin here, co-founder of Spacelift. Even though I strongly believe the OpenTF fork could open up incredible possibilities for the community (I could go on and on about it), it is an equivalent of a civil war. It doesn't serve the community and our only interest is in the continued strength of the community that we continue to build for. Based on my immense respect for what's been built under Hashi's umbrella I'd ra…

it's not war

hashicorp has decided they don't want to contribute to open source any more

they're totally within their rights to do so, and it doesn't harm anybody; it's not the equivalent of going around blowing up buildings, raping women, and napalming children. at most we can wish they had continued doing the beneficial things they were previously doing

maybe they'll change their minds, as you say, but that's no reason for the community to sit around twiddling its thumbs hoping for such a change. what's important now is that the people who are still willing to cooperate can do so successfully, and that's what opentf is about

that's even more obviously not the equivalent of going around blowing up buildings, raping women, and napalming children. it's very much the opposite, in fact

it's unclear to me which of the parties you intend to accuse of doing the moral equivalent of burning innocent people alive en masse, but either way, maybe you should think about walking back that rhetoric a bit

Re: The OpenTF Manifesto

#246
post #76

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.

Any reason why you don’t like cloudFormation or the SDKs?

Re: The OpenTF Manifesto

#247
post #234

Earlier quoted context omitted.

It should worry you - it hurts the ecosystem. Terraform is just a tool. The providers, modules, not supported by HashiCorp, is what makes Terraform useful. Ige the ecosystem dies, Terraform becomes useless.

The ecosystem outside of providers is far less important than people like to claim. Open source modules are almost all poorly scoped, often just wrapping a single resource completely unnecessarily - simultaneously over- and under-abstracted. It's also a huge security risk to pull them in.

The only providers I have ever used in production, or would likely ever consider using would be published by Hashicorp or the software vendor for the resource being managed (for example [1]). Much would need to be done to trust any other third party without good reason.

I have had similar experiences poking around other tf providers which were of apparently low quality.

[1] https://registry.terraform.io/providers/elastic/ec/latest/do...

Re: The OpenTF Manifesto

#248
post #186

Earlier quoted context omitted.

Honest question, what do you consider config vs infra? What is infra if not configuring a system to run?

Infra is defining the servers that should be running. Config is writing configuration files to a running server. Cloud blurs the line, since a lot of cloud offerings are managed where you're really doing both at once when you define the managed offering.

Let's not continue this cargo cult mumbo jumbo.

Terraform is literally a program that looks at a declarative configuration file, looks at a state file, queries some APIs, and then submits some API calls. That is all it does.

There is no "infrastructure", or "config", or "cloud". It's literally just calling HTTPS APIs, the same way it would call a system call or a library function. Call function, pass input, receive output.

There is no magic sauce. There is no difference between it and any other tool that has a declarative configuration, a state, and operations to try to change things to match a desired state.

It's all configuration management. The words "infra", "orchestration", "cloud", etc is marketing bullshit. It's all just software.

Re: The OpenTF Manifesto

#249

I appreciate the letter and trying to work with Hashicorp -- I used to have a ton of respect for Hashicorp. But honestly... at this point... ...just fork it into a foundation. Don't wait for Hashicorp's response. I get wanting to have the appearance of working with Hashicorp, but we've been shown again, and again, and again, and a-fucking-gain that private corporations cannot be trusted to maintain public goods. Only…

Marcin here, co-founder of Spacelift. Even though I strongly believe the OpenTF fork could open up incredible possibilities for the community (I could go on and on about it), it is an equivalent of a civil war. It doesn't serve the community and our only interest is in the continued strength of the community that we continue to build for. Based on my immense respect for what's been built under Hashi's umbrella I'd ra…

As a user and collaborator of TACOS, agreed that it could open up opportunities. Though I echo trade-offs (as in other replies) that it could start a civil war that makes it difficult for end users and collaborators -- reminds me of Python2 -> 3, Presto/Trino, and many other stories. Pledging resources is a great approach.

Re: The OpenTF Manifesto

#250
post #175

As an end-user, not competing with HashiCorp, this change doesn't worry me. According to their FAQ [1]: 10. What are the usage limitations for HashiCorp’s products under BSL? All non-production uses are permitted. All production uses are allowed other than hosting or embedding the software in an offering competitive with HashiCorp commercial products, hosted or self-managed. 24. Can I host the HashiCorp products as a…

Even if you don't mind abiding by the terms of the BSL, the licensing change is a signal that Hashicorp is in dire straits and doesn't know how to operate as a sustainable business. They're flailing about trying to increase revenue, and in so doing they're removing one of the core components (the open source licensing) that made their tools ubiquitous to begin with. And what will their next cash grab be? Here's the k…

Giving away most of your product for free and selling commercial services on top when it's very easy to compete with you on that front is.... well it's not a sustainable business model.

It would be troublesome if any of the vendors at $work past or present went bankrupt, this is the nature of having external vendors. I am not particularly concerned.

I was not the biggest fan of Terraform in the first place, I don't like some of the language choices, but it works better than anything else that exists out there.

Post reply on HN