Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fishnchips
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
fishnchips
3y ago
BoJo legacy lives on!
92.
▲
by
fishnchips
3y ago
Should work out of the box TBH, IIRC the CDK works as a preprocessor.
93.
▲
by
fishnchips
3y ago
> multiple stack deployment, chained deployments Intriguing ideas. Would you mind elaborating or - even better - open issues [0] explaining the concepts to gauge the community interest? [0] https://github.com/opentofu
94.
▲
by
fishnchips
3y ago
> designer that can come up with some crazy lore of terraforming with tofu I have a feeling that the designer may find it... challenging.
95.
▲
by
fishnchips
3y ago
I think this [0] may be what the OP meant. [0] https://en.m.wikipedia.org/wiki/Great_Plan_for_the_Transform...
96.
▲
by
fishnchips
3y ago
Sure. But names including “terra” would be even more risky. Someone suggested LunarSpoon though and I personally found it hilarious.
97.
▲
by
fishnchips
3y ago
Wholesome and sustainable :)
98.
▲
by
fishnchips
3y ago
Curious how long this one lasts.
99.
▲
by
fishnchips
3y ago
Ah, just noticed. The founder is Polish. That explains the name. As a Pole, I actually greatly appreciate these Slavic names in tech.
100.
▲
by
fishnchips
3y ago
Also in Polish and other Slavic languages probably, too.
101.
▲
by
fishnchips
3y ago
> skeptical of OpenTF's motives Acknowledged, there are always self-serving motives involved. Generally things don't happen without a reason. But we donated the project to a foundation, and will over time build (and fund) a ded
102.
▲
by
fishnchips
3y ago
Oh, the core license change is irrelevant here, and the providers are MPL. I was just responding to a comment on how AWS didn't care if the provider was open. IMO there's value for them in it being open.
103.
▲
by
fishnchips
3y ago
> were too lazy or hostile to negotiate a deal with Hashicorp And how do you know about any dealings any of us did or didn't have with them, now or in the past? Are you privy to any of that? > lack of competency in execution, pla
104.
▲
by
fishnchips
3y ago
I know that you're commenting in bad faith and if it weren't for commit messages, you'd have found some other reason to spew hate. But I know that your comment will be read by people who don't come with an agenda, so I&#
105.
▲
by
fishnchips
3y ago
Fair point, I think we can fix that. Thanks for highlighting that.
106.
▲
by
fishnchips
3y ago
AWS probably doesn't care much for it being closed either. But the benefit of being open is that folks can investigate, report and fix bugs. For example, at Spacelift we found a fascinating corner case where an RDS DB could be dropped
107.
▲
by
fishnchips
3y ago
Good point, we should enforce squash merging.
108.
▲
by
fishnchips
3y ago
GitHub has this "compare" functionality - this gives you a diff between where we forked and the current "main" - https://github.com/opentffoundation/opentf/compare/8a085b427...
109.
▲
by
fishnchips
3y ago
> main product Well that's the core problem - what is the product here. Terraform Cloud and Terraform Enterprise are products for sure. They're not open source, though. Is Terraform a product? Well, it doesn't do anything
110.
▲
by
fishnchips
3y ago
Marcin here, one of OpenTF folks. I think the redeeming factor of Terraform is not the language itself, though I really like the fact that it's not a programming language. But I think the redeeming factor is the tool that interprets
111.
▲
by
fishnchips
3y ago
It's around that time that it became impossible to ask for forgiveness rather than permission, at least where I worked (2007-2014).
112.
▲
by
fishnchips
3y ago
Correct, the manifest is optional.
113.
▲
by
fishnchips
3y ago
The publishing process for the public registry is very prescriptive, and there is indeed a manifest file involved - https://developer.hashicorp.com/terraform/registry/providers...
114.
▲
by
fishnchips
3y ago
For their own managed providers they no longer provide binaries in GitHub releases, and serve them from their own servers instead. Which feels like a trap BTW.
115.
▲
by
fishnchips
3y ago
More or less, yes. This is a complex legal topic. Also, we need to make sure we don't violate the new registry T&Cs.
116.
▲
by
fishnchips
3y ago
Regardless of how they behaved towards us in the more distant and very recent past, I still hope there's a way out of that, and I will not be the one to start the war. It's not my desire to portray HashiCorp in a bad light, and I
117.
▲
by
fishnchips
3y ago
I’ve never given much credence to conspiracy theories but a project that connects AI, crypto and biometrics sounds like something that could play a role in the next Bond movie.
118.
▲
by
fishnchips
3y ago
Yes, and perhaps backends could work in a similar way, too? One other thing was that I was thinking whether these plugins really need to be local. A remote gRPC server could possibly work as well, I guess? Again, pure personal speculation.
119.
▲
by
fishnchips
3y ago
Pure personal speculation here, even though I'm one of the OpenTF folks. If one wanted to make secret encryption ultimately flexible, it could become a type of extension like provider, which would work as a sidecar and simply encrypt a
120.
▲
by
fishnchips
3y ago
I don't agree with your sentiment one bit but I will not try to change your mind. At the end of the day what matters is the outcome of the project for the community. So let's all take a deep breath and revisit this in a few months
More ›