231–240 of 260 posts
It also makes me think if Fujitsu's interconnect for their crazy HPC ARM chips (PDF warning): https://www.fujitsu.com/global/documents/about/resources/pub...
That there is a pretty brilliant way out of a scary trademark situation. Props to the braintrust that made it so.
That there is a pretty brilliant way out of a scary trademark situation. Props to the braintrust that made it so.
We pretty much talk in terms of "let's terraform a new environment" at places where we use it.
Earlier quoted context omitted.
Everything has gaps that need to be filled, the main point is that the object I send is the same shape and schema as the API, same for their responses and the data in the system. TF under the hood is using these APIs through an abstraction. I say "go to the APIs" as (1) bypassing abstractions (2) in CUE, we can import the existing TF resource schemas from the Go types, or from the OpenAPI schemas. There are 2 camps i…
CUE or any other configuration language is orthogonal to whether or not a meaningful declarative provider (whether TF, Pulumi or anything else!) can be generated from a cloud provider API specification. The only cloud that offers a really declarative API at all is Azure, via Resource Manager. For AWS, since most APIs are request-response focused (AttachENI, DetachVolume and so forth), something has to tie all that to…
100% agreement
What CUE potentially makes great is going from what the API spec has available to what we need by keeping the enrichments by us in the same space, so we merge or unify into a single space, without having to write code in the imperative sense. You get to stay in a logical space that will ensure what you write remains self consistent. It will catch the gaps and issues earlier.
I'm not aware of any config language or other technology that looks to make this processes as good as CUE can, except maybe sprinkling some of that magic LLM dust on the problem too, which CUE will help in double checking as well
I predict that it will be commonly known as "Tofu", which is a wonderfully snappy name. Almost too good for this kind of project.
Earlier quoted context omitted.
What was the trademark situation?
It was called OpenTF or OpenTerraform. Hashicorp might have had an issue with using the name Terraform.
[0] https://github.com/opentofu/opentofu/issues/273#issuecomment...
Who eats tofu with a fork?