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

hey there! any branch name is fine, we run the tests on PR, so just send the PR upstream and ping us and we'll take a look!

Thanks! Was a really tiny fix (<https://github.com/pulumi/pulumi-docker/pull/311|#311>). Would really appreciate hearing feedback if I missed anything I should be doing for a PR so I know for future

<@U02KSGGJA86> unfortunately your fix won't quite work, because the SDK folder is automatically generated from the resource itself :disappointed:

Ah might have jumped the gun a bit then, any chance you could please point me in the right direction for what controls that?

it'll need to be a codegen update, which is out my wheelhouse ability unfortunately...

I'm confused about how the codgen works. I saw a <https://github.com/pulumi/pulumi-docker/commit/e4ad7804e8194d710b40749e40e6534cac928cb6|previous PR> which had edited the same line of code, was that edit generated from <https://github.com/pulumi/pulumi-docker/blob/master/provider/cmd/pulumi-resource-docker/schema.json|this schema>?

i could be wrong, let's leave the PR open and I'll get some from eng tomorrow to take a look

Ok cheers, I've just never worked with codegen before so will be happy to learn more if I've got things mixed up

That's not a codegen file, it's handwritten - so you're all good <@U02KSGGJA86>

It's one of the few overlays in the docker provider... most of the rest of it is generated but these files are handwritten: <https://github.com/pulumi/pulumi-docker/blob/master/provider/resources.go#L141-L147>