This message was deleted.

Looking at the

build_sdks

make target, I don’t see anything that packages them up into a tarball, and I don’t see anything in the

pulumi-package-publisher

action tarballs them either. I must be missing some step in the setup?

Hey @bright-receptionist-28471 - we've been working on an alternative templating that might be a bit easier to start with. Would you mind kicking the tires on it? I think it'll get you started a bit more quickly, though the downside is that right now it configures GitHub workflows as if it were a repo in the Pulumi org (not too different from the release.yml you saw).

Hey @orange-policeman-59119 I have the setup working now, but I’m happy to try walking through the process with the new repo to give feedback if that’s helpful

We're looking to migrate away from repos to add some smarts to the boilerplates, as users need to select the appropriate bridge adapters for upstream providers using the TF SDK, TF Plugin Framework, or both. If you're interested, clone https://github.com/pulumi/ci-mgmt And in provider-ci, copy and edit one of the "wip/*.config.yaml" files appropriately to

$yourProviderName.config.yaml

$ make bin/provider-ci

The

wip/test.sh

script shows how to invoke the tool - but it'll rm -rf a directory by default so I won't suggest you run it without looking. You'd run it like:

./wip/test.sh $yourProviderName

And it should give you a complete repository a couple directories up, named

pulumi-$yourProviderName

.

Maybe I’m looking in the wrong place, but I don’t see a

wip

directory under

provider-ci

https://github.com/pulumi/ci-mgmt/tree/master/provider-ci

Ah, I neglected to tell you the branch. It's on the branch

friel/tf-boilerplate-v2