https://pulumi.com logo
#package-authoring
Title
# package-authoring
b

bland-address-49163

02/23/2024, 12:35 PM
I'm currently considering wrapping an existing terraform provider with pulumi. How much time would you - very roughly - guess does this take in practice, especially with ongoing maintenance? I know this is very vague, so I'm not expecting any accurate numbers. I'm just wondering if this is something in the area of "initially 1-2 days, then a few hours every few months to keep the package updated" or if I should expect a lot more effort. I'm very curious to hear from people who've done this in the past.
b

big-architect-71258

02/23/2024, 12:41 PM
@bland-address-49163 If you're using my Cookiecutter Template https://github.com/tmeckel/pulumi-tf-provider-cookiecutter and depending how well the target TF provider is adhering to the GO module definition you are up and running with a wrapped provider in minutes. I'd recommend publishing the wrapped provider via Pulumiverse https://github.com/pulumiverse/ (what is the default in the Cookiecutter Template) which spares you from configuring all required package registries.
b

bland-address-49163

02/23/2024, 12:47 PM
Thanks! Do you know if it's possible (or even if it makes sense) to try this locally first, before publishing it to a registry?
b

big-architect-71258

02/23/2024, 12:50 PM
@bland-address-49163 Of course. I always test a newly wrapped provider locally using the YAML language binding, because it only requires the provider executable in the $PATH. The Cookiecutter template will also create a README-DEVELOPMENT.md document which describes how to work (develop) on the mapped provider, including local tests.
b

bland-address-49163

02/23/2024, 12:54 PM
Thank you, I'll give it a go!
b

big-architect-71258

02/23/2024, 12:55 PM
@bland-address-49163 Because I always seek to improve the template and it's documentation, it would be great if you could share your experiences.
b

bland-address-49163

02/23/2024, 1:00 PM
Yes, I will
2 Views