Our great sponsors
-
pulumi-terraform-bridge
A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
-
Pulumi
Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
pulumi-aws
An Amazon Web Services (AWS) Pulumi resource package, providing multi-language access to AWS
-
pulumi-kubernetes
A Pulumi resource provider for Kubernetes to manage API resources and workloads in running clusters
I think they might use their (pulumi-terraform-bridge)[https://github.com/pulumi/pulumi-terraform-bridge] to generate some of their provider code from the corresponding Terraform providers? (This page mentioned some of their "most interesting providers" are created like this)[https://www.pulumi.com/docs/intro/vs/terraform/#using-terraform-providers].
That is not true. You can actually look at the source code here https://github.com/pulumi/pulumi
Pulumi uses terraform providers to schematize the CRUD options for some cloud providers. Part of the difficulty with any infrastructure as code offering is that your favourite cloud provider doesn't always provide a full API spec, so we need to somehow figure out what resources can be created, what parameters are available to those resources etc. We take the terraform provider, look at the available operations for that provider and then turned it into a Pulumi schema, which can then be read by the Pulumi engine. If you take a look here you can actually see that generated schema for AWS.
We are working with many cloud providers to have them publish full API specifications so we can generate the schema directly from the upstream source. If you look at our Azure Nextgen it's generated from the published Azure specification. This also means our Azure provider has full coverage of all the Azure resources! The same can be said for our Kubernetes provider