cube2222

37 ms·

451.
by cube2222 3y ago
Mostly trademark issues, really.
452.
by cube2222 3y ago
Thank you for the kind words, they are very appreciated! I'll make sure to relay them to the rest of the team :)
453.
by cube2222 3y ago
> opentf doesn’t just cause a fragmentation We're trying to remain as compatible on all fronts as possible, and our registry will too, so I wouldn't be attributing the fragmentation to OpenTF.
454.
by cube2222 3y ago
Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all provider
455.
Harness Joins OpenTF Initiative(harness.io)
16 points by cube2222 3y ago|0 comments
456.
by cube2222 3y ago
> If we are to accept that the OpenTF foundation is going to be a better maintainer of terraform we need something better than "Hack on opensource if you want to!" The plan is for the foundation to employ dedicated engineers th
457.
by cube2222 3y ago
Tests are all green, actually! We believe we've even resurrected a large number of previously broken tests. Really, there's a few things, like getting rid of trademark infringement and setting up some basic community guardrails, t
458.
by cube2222 3y ago
We actually specifically don't want this to be our employees. Rather, we want the foundation to employ the maintainers (whom we'll pay for). Which is partially because of the bad incentives the former approach creates. Disclaimer
459.
by cube2222 3y ago
This is actually a feature I'd love OpenTF to have and am quite passionate about, personally. My plan is to submit it once we have the RFC process in place. Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the O
460.
by cube2222 3y ago
Making sure there aren't any trademark infringements left, that we have some basic community process in place, etc. There's unfortunately a bunch of these things we have to do before we can publish. We created a public roadmap rep
461.
by cube2222 3y ago
Congrats! I've played with Phind a few times, and it's definitely one of the cooler products to come out of the LLM boom.
462.
by cube2222 3y ago
We're planning to stay 100% backwards compatible, and in the early stages we definitely want for it to be easy for people to migrate back and forth between both tools - even have teams with different engineers using different tools. DS
463.
by cube2222 3y ago
Initially we strive for 100% interoperability. The provider framework has been kept MPL, as have the providers, so we will keep being compatible. We will see what the longer-term future brings, and we'll react accordingly. We also have
464.
by cube2222 3y ago
I'll join the other members of the OpenTF Initiative who've already commented - I'm honoured to be a part of this effort and can't wait for us to push this forward in the following days, weeks, months, and years! It&#x27
465.
OpenTF announces fork of Terraform(opentf.org)
1711 points by cube2222 3y ago|486 comments
466.
by cube2222 3y ago
On a related note, if you haven't seen it yet, make sure to check out the OpenTF Manifesto[0]. More info coming on Friday! [0]: https://opentf.org Disclaimer: Work at Spacelift
467.
by cube2222 3y ago
> cloud-based TF instances Not sure what specifically you mean with this. Anyway, the devil’s in the details, of both the license as well as the internal architecture of our system. I can’t share more here, but if you’d like to learn mor
468.
by cube2222 3y ago
Thanks, very appreciated!
469.
by cube2222 3y ago
> 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 announc
470.
by cube2222 3y ago
Their FAQ states they'll backport security fixes under the old license until the end of 2023. Disclaimer: Work at Spacelift
471.
Spacelift’s Latest Statement on HashiCorp’s BSL Adoption(spacelift.io)
10 points by cube2222 3y ago|0 comments
472.
by cube2222 3y ago
Also, update from Spacelift, we believe that we are not in violation of the new license, you can find more details in our today's announcement[0]. We nevertheless support this initiative, though, as written in the article itself. [0]:
473.
by cube2222 3y ago
It's actually much older than that. I think it was coined by CloudPosse with this video: https://youtu.be/4MLBpBqZmpM (December 2020)
474.
What HashiCorp’s license change means for our customers(spacelift.io)
230 points by cube2222 3y ago|262 comments
475.
by cube2222 3y ago
Not sure if with shift-left you mean specifically shifting left infracost and FinOps or general Infrastructure-as-Code shift left. In case it's the latter, I can recommend Spacelift[0] - a specialized CI/CD tool for IaC and suppor
476.
by cube2222 3y ago
> An Attr is a key-value pair. So s/KeyValuePair/Attr/g? Re varargs vs record, varargs are usually used in Go because they're very ergonomic to write inline, so they work very nice with loggers. Group sounds like a fa
477.
by cube2222 3y ago
What else would you expect from a structured logging package? To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
478.
by cube2222 3y ago
Could you expand what you mean? When skimming it I mostly saw the common API structure that I usually see in libraries / write myself when I need a logger, so I generally welcome the standardization.
479.
by cube2222 3y ago
In the Llama 2 paper benchmarks they did mention that Llama 2 is much worse at any kind of code generation than the OpenAI models, they were optimizing for conversational / natural language use-cases.
480.
by cube2222 3y ago
You wrote your comment as though it's not ok, while you can play it offline in single player just fine. But there's optional Cross-Platform save sync (independent of the steam one) and multiplayer. Anyway, as a person who bounced

More ›