This message was deleted.
# generals
sparse-intern-71089
08/24/2020, 9:22 PMThis message was deleted.
w
white-balloon-205
08/24/2020, 9:42 PM
Today - the Pulumi Azure provider is based on the upstream Terraform Azure Provider. Our goal is to be up to date within 48 hours of the upstream provider. The upstream Terraform Azure Provider is a little more inconsistent - but for most features is kept very up to date with new services and features in Azure.
Notably - for Kubernetes - we are today up to date within minutes/hours of new releases of the Kubernetes API (1.19 is releasing tomorrow!) because we have our own provider that is derived nearly completely from the Kubernetes OpenAPI specs (that is, we do not have a dependency on a Terraform Provider for Kubernetes).
We also have some exciting new work in this space which we'll be sharing more on in the coming months - stay tuned!
k
kind-mechanic-53546
08/25/2020, 8:24 AMIn addition to what Luke said, this is a problem with all IaC tools and I've personally found Pulumi to have great traction and be extremely responsive to issues and feedback from the community
kind-mechanic-53546
08/25/2020, 8:25 AMTo the extent that Terraform (and hence Pulumi) are ahead of CloudFormation in some cases which is crazy
kind-mechanic-53546
08/25/2020, 8:26 AMThis illustrates the view that IaC is a secondary concern for some teams (all?) in the major cloud providers
kind-mechanic-53546
08/25/2020, 8:27 AMAll services should really be IaC first and console second unless there is a really good reason (IAM I can see potential issues around)
kind-mechanic-53546
08/25/2020, 8:28 AMThe more advocacy around IaC first services we have, the better our lives will be 🙂
👆 1
w
wet-noon-14291
08/25/2020, 8:23 PMThis is all good and also something that I wasn’t concerned about. I asked for an official post one can point to when others mention this as a concern.
👍 1