My experience with Pulumi and AWS CDK is absolutely brilliant in this regard, hopefully good DevOps/SRE/WhateverNewTerm practices and patterns will reassemble good software development practices in the future.
In my view, this is the insight and value proposition that sets cue apart from everything else, including general programming languages.
Inheritance + property overriding is the source of most problems in configuration because you can never know if a value is the source of truth.
In what sense is CUE not a real language?
Personally, on one hand I know allowing computations into configuration immediatly destroys any hope of having a tidy, rational schema in real word projects.
On the other hand though, i do believe configuration and code should be build with related tools, possibly the same tool- or at least tools using the same syntax!
(a bit like the json syntax is the same as a Python dict syntax, except this is the terrible example that is so poorly thought out that does more harm than good)
This unlocks a much greater degree of freedom and power than all the gluing together technologies that we have to do...
My 2c - thus far, i've found the language features enabled by this constraint much more useful than the expressiveness lost - at least, for the purposes i've chosen.