This message was deleted.

@cuddly-barista-79466 It’s a fairly simple job to create a bridged provider

So my question comes from this repo https://github.com/pulumi/pulumi-terraform which explains the bridge stuff. And forgive my lack of understanding but, how is this used to create a bridge provider? Does this program build it, do i need a new project that uses this repo as the base? Do, i need a new project that calls this tf bridge project? I feel like i am missing some details on getting started with create a new TF Bridge provider

Here’s a nice small example: https://github.com/pulumi/pulumi-random

Right. I get the examples. But what is building all the scaffolding for the pulumi provider in the go project? Or how much can I copy from an existing example? Is there pulumi provider bridge generate blank project? This is where i am stuck at, not being a Go developer

Ah, I see

Sorry if it’s not apparent to me

Right now I think it’s pretty much cargo culted from repo to repo, there’s not necessarily a coherant approach that you are missing

Gotcha. I get that

Is lack of BigIP blocking you?

I am trying to make the case to my team that we can use pulumi for On-Prem IAC

I opened https://github.com/pulumi/pulumi-terraform/issues/293 on the topic of having an easy to use template for creating new Terraform-based providers. Definitely something we can make easier. Many users have been successful starting from something like https://github.com/pulumi/pulumi-random and manually updating to the desired provider. We are also very happy to help with this process either during initial bringup, or in moving the provider into the

pulumi

organization and adding it to our test matrix. (though as @stocky-spoon-28903 notes, not sure what the test approach looks like for BigIP given there is custom hardware required for testing).

so things we need to put into IAC would involve, vsphere, big-ip, infoblox(Maybe), Active Directory(OUs, DNS, Groups)