hello, we are trying to generate a pulumi provider from terraform using the Terraform Bridge Provider Boilerplate. We have encountered an issue in the test workflow because after the go sdk is built git-status-check-action fails as there are changes in upstream. We have created a patch and after the sdk is generated there are still some staged changes on the upstream branch. We are not sure if we should commit these changes or what exactly the inteded way to fix this is. Was hoping you could help us

Any reason you can't use the any tf provider ability? https://www.pulumi.com/blog/any-terraform-provider/

We are maintaining the Ionoscloud terraform provider and would like to offer our customers an easy way to also use pulumi, we feel like generating the sdks ourself allows for more control over how the SDKs look

@plain-arm-75429 can you post the link to your git(hub) repo?

hello, sure, here it is, https://github.com/ionos-cloud/pulumi-ionoscloud for the time being we are ignoring changes in the upstream inside the workflow

@plain-arm-75429 when I build

main

, I get quite a lot of changes. It seems the generated SDKs are out of sync with the settings you made in

provider/resources.go

. I suggest you first start by committing these changed SDKs into Git.

Hello, sorry for the long time but I had to focus on other projects and wanted to get back when I could focus on this. I have rerun the build and commited everything to the feat/add-python-sdk branch, where we try to add both the python and nodejs sdk. For the changes we talked about above we are still ignoring upstream, but we have a new issue. The generated NodeJS sdk seems to have a wrong version in package.json ("version": "${VERSION}",) and I am not sure why it is generated like this