No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@UCWG26BH7> there’s this issue open <https://github.com/pulumi/pulumi-terraform-bridge/issues/635> which has been open for a while but without any replies. I generally would spend some time and send a PR, but I don’t have the capacity to go through a completely new repo at the moment. Is there any chance we could get anyone to have a look as the defaulting of a variable shouldn’t be too much of an effort who is familiar with the codebase already. Alternatively, I’d be interested to learn more about how the bridge fits into the providers if they’re not actually coming from a TF source :thinking_face:

Ah, I see now it’s based on the deprecated `mysql` TF provider…

Is there a related issue that means that issue affecting you? Are you trying to bridge a provider?

It’s actually related from this issue in the `pulumi-mysql` package <https://github.com/pulumi/pulumi-mysql/issues/131>

I don’t have any thoughts, I did notice the issue is closed, is you could open a new issue I can ask the providers team to take a look 

<https://github.com/pulumi/pulumi-terraform-bridge/issues/635> this issue isn’t closed :thinking_face:

sorry, i meant this one is:
<https://github.com/pulumi/pulumi-mysql/issues/131>

So, the issue I believe is actually in the `pulumi-terraform-bridge` , not the `pulumi-mysql` provider. What basically happens is that when a configuration value coming from an environment variable is meant to be `null`, it instead gets defaulted to an empty string which causes things to break

<@UCWG26BH7> is there anyone we could nudge?