3 ms·
CUE or any other configuration language is orthogonal to whether or not a meaningful declarative provider (whether TF, Pulumi or anything else!) can be generate
by jen20 3y ago
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 together to make a resource-focused API.
- verdverm 3y ago> CUE or any other configuration language is orthogonal to whether or not a meaningful declarative provider 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