Can anyone tell me has the process of writing a cr...
# package-authoring
g
Can anyone tell me has the process of writing a cross language component package gotten any better? In this video they keep alluding to the situation evolving that less “boilerplate” work will be needed in the future. That was two years ago:

https://www.youtube.com/watch?v=4psf6WVLxtY

It has been hard to find good documentation on this
Specifically removal of go and less find replace etc
l
Having had to dig through it all recently, I think it has gotten slightly easier and less reliant on go, but it's difficult to find working examples of it. It took me a solid couple of days to get a modern TS provider working in other langs
b
no, it’s still a nightmare 😞
g
Ugh that’s sad. Makes it hard for me to sell if reuse is restricted to a single language as ops folks are going to want python and web TS (for instance).
b
i’m available for consulting if that’s something you’re interested in exploring, I can help you build one
g
I think I have it working thx to your video. Just template was out of date and required a lot of updating. The find/replace stuff was tedious obviously. Feels like a tool to scaffold something up would be warranted/doable.
b
yeah totally get it
g
I know AWS CDK works differently obviously (I am the guy who commented on JSii on the original stream haha), but that cross language stuff was a lot easier to get going with.
Unfortunately I’m working in Azure these days so not an option.
@billowy-army-68599 any chance you could point me at how to troubleshoot? I built all the provider plugins. Installed the sdk package. Installed the provider from the tar file. When I run Pulumi up it tells me it cannot read the plugins stdout:EOF? I’m on macOS (m2 if that matters). I installed the arm provider….kind of at a loss
b
it could be any number of things, hard to know where to start
g
Exactly and without a good error I’m kind of screwed
My instinct was the provider didn’t build correctly but there was no error around that
Looks like a code signing issue if I’m on the right track. Thx anyway @billowy-army-68599
Woo self signed for the win!!!!!