The OpenTF Manifesto

Post by Kamq » Wed, Aug 16, 2023, 3:06 AM UTC

tootie wrote: post #150

bloopernova wrote: post #125

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.

I'm not Hashicorp, but I mean look at Docker. They built the most valuable devops tool of the last generation and can barely muster a viable business. Why would Hashicorp give the slightest worry to losing thousands and thousands of non-paying customers? The upside is lots of money and the downside is loss of halo. Honestly, it's an unfortunate game of expectation setting. If I wrote an open letter decrying Salesforc…

Post by time0ut » Wed, Aug 16, 2023, 4:08 AM UTC

linuxdude314 wrote: post #295

time0ut wrote: post #149

As a long time Gruntwork customer, contributor, and fan, it is really nice to see them stepping up as thought leaders here. They run a great open source community already. Our DevOps team has been buzzing all day with what we are going to do. For now, we are staying pinned to the last open source version of Terraform and will likely follow Gruntwork's lead when the time comes.

If your company isn't building a product based on terraform, why are you doing anything?

Post by waynesonfire » Wed, Aug 16, 2023, 4:57 AM UTC

lmm wrote: post #288

enneff wrote: post #242

Earlier quoted context omitted.

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 va…

> The costs of maintaining a fork are significant Why? If we have tooling or workflows that assume forks don't happen, maybe we can fix those. Forking should be cheap, easy and frequent.

Post by AaronFriel » Wed, Aug 16, 2023, 5:09 AM UTC

verdverm wrote: post #301

jjnoakes wrote: post #297

Earlier quoted context omitted.

In general maybe, but in the specific context above, I think calling that loop declarative is accurate, and laughing at that classification is a poor response rooted in a deep misunderstanding.

import pulumi from pulumi_gcp import storage bucket = "hof-io--develop-internal" name = "pulumi/hack/condition.txt" cond = False msg = "running" cnt = 0 while not cond: cnt += 1 key = storage.get_bucket_object_content(name=name, bucket=bucket) print(cnt, key.content) if key.content == "exit": msg = "hallo!" break pulumi.export('msg', msg) pulumi.export('cnt', cnt) --- 769 exit 770 exit 771 exit 772 exit 773 exit 774…

    import * as publicIp from 'public-ip';

    new someProvider.Kubernetes.Cluster('cluster',
      {
        apiServerAccessProfile: {
          authorizedIPRanges: [await publicIp.v4()],
          enablePrivateCluster: false,
        },
      }

Post by lmm » Wed, Aug 16, 2023, 6:13 AM UTC

waynesonfire wrote: post #316

lmm wrote: post #288

Earlier quoted context omitted.

> The costs of maintaining a fork are significant Why? If we have tooling or workflows that assume forks don't happen, maybe we can fix those. Forking should be cheap, easy and frequent.

Right below your comment was another comment that started with, "The truth is that a fork hurts everyone." So, which is it?