pulumi-tf-provider-boilerplate VS mazzle-starter

I'm interested in how to take existing high-quality Terraform Providers and convert them into Pulumi providers. Can you discuss the future roadmap for this project and any others around this effort.

The documentation on https://github.com/pulumi/pulumi-tf-provider-boilerplate would benefit from more examples and further explanation. I had to reverse engineer the pulumi-aws provider to be able to wrap an existing TF provider.

> If Pulumi didn't bless it, it doesn't exist in Pulumi's world.

That has not been my experience. I have personally ported a Sentry TF provider into Pulumi, and I will grant you that their docs and examples are bordering on active user hatred for exercising the process, but it does work:

https://github.com/pulumi/pulumi-terraform-bridge#adapting-a...

https://github.com/pulumi/pulumi-tf-provider-boilerplate#rea...

What mystifies me about that situation is that I do actually appreciate the amount of silliness that is required to avoid using Pulumi cloud: they are not financially incentivized to make that easy, but I'd guess a lot more folks would nope right out if they didn't make it possible

However, I would think they'd want to make ingesting a TF provider into Pulumi as smooth and reliable as possible, so they don't have people close their browser tab when they don't find a supported provider for Pulumi but it exists in TF

I take advantage of I/O being parallel in Python in my mazzle continuous integration pipeline tool. I'm not sharing mutable state.

I spin up a graph of python Threads and each joins others in a graph. This way we can run graphs in parallel. See this graph - the parts that look like this:

dependency -> {parallel1; parallel2; parallel3} -> postparallel

parallel1, parallel2, parallel3 can run in parallel in a separate python thread because the IO is parallel.

postparallel joins parallel1, parallel2, parallel3 and waits for them all to complete.

Where parallel1-3 is things like ansible, packer (slow), AMI builds, chef runs etc.

https://github.com/samsquire/mazzle-starter/blob/master/arch...

I use a tool I wrote to layer my infrastructure with layers called components and I configure it with a Graphviz file.

My tool, called mazzle (previously devops-pipeline) would run parts of the graph that can run in parallel in parallel. It can also run parts of the build on SSH workers. You bring up the workers at the beginning of the build.

Here's an example of a graph generated from graphviz file: https://github.com/samsquire/mazzle/blob/master/docs/archite...

This graph brings up a hashicorp vault server, Java application, bastion proxy etc.

here's the graphviz file: https://github.com/samsquire/mazzle-starter/blob/master/arch...

It describes the ordering of the infrastructure, the invocation of Ansible, packer, shell scripts to set up vault etc.

The idea is to be able to bring up a new environment by changing one parameter. There's a React GUI too.

https://devops-pipeline.com