[icedchai]

Cloud agnostic? Not really. All the resources are cloud specific. You can't configure anything of any complexity without knowing details about your specific provider.

Low level? It's about as far from "low level" as you can get. I would barely call it a programming language.

That being said, I do think it is a worthwhile skill to learn.

[jjice]

I interpreted those things being listed as individual items in a list, not one continuous thing, so I assume the "low level programming" is it's own task.

Also, I think a certain level of cloud agnosticism is possible. A lot of things like App Engine-esque services and FaaS can be boiled down to a core subset that can be agnostic. Once you get into managed queues and such, then you start losing some agnosticism for sure.

[dasil003]

You're right Terraform is not cloud-agnostic in terms of resources, but I'd argue you wouldn't really want a truly cloud-agnostic configurator at the resource level as it would be far too leaky an abstraction to have any reliable value. On the other hand, in terms of a cloud configuration system as a whole, Terraform's state management and sequencing resolution is provider agnostic, which I think makes it a much better investment than any cloud-specific orchestration system.