This message was deleted.

Only one data-point from me. We are using Python (and have more infrastructure engineers comfortable in Python). In standing up an EKS cluster, the guide for the TS library definitely seemed more robust / developed. I ended up being able to make Python work for me though. That's all I've got 😄 Curious to see what others say

my company is going to be using the dotnet automation API on a pretty big internal web API project for automated deployments (all of our stacks have a dotnet backend). I hope that doesn't mean we might eventually fall behind on feature parity 😅

we started using Python and migrated to TS - we found package management to be a bit easier on the TS side with npm packages if you have multiple projects that need to be packaged in different ways

Our company is advising teams to use whatever language the team normally uses, so there is less of a learning curve.

thing is, the team normally uses go, but there's no dynamic providers in go and writing actual providers is a much more serious undertaking than "inherit from a class and implement 4 methods". So there is a learning curve anyway

I'm with you there, .NET doesn't have one either. I'm hopeful they come up with something.