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

I’d appreciate any pointers you have on getting it fixed

We have a race condition that is causing issues - see <https://github.com/pulumi/pulumi-docker/runs/2763541149?check_suite_focus=true#step:20:228|https://github.com/pulumi/pulumi-docker/runs/2763541149?check_suite_focus=true#step:20:228> for the issue we are running into

They were skipped at major upgrade version as v2 of the api is not compatible with v3 of the api and our testing framework can’t handle that very well

But not they can be renabled again but doing that gives this error above

ah I see. If I make a PR to fix the CacheFrom problem, will it get accepted since the testing framework can’t verify if the fix works?

I can verify it locally before we can merge so it would be more than welcome 

awesome! I’ll do my best to get that out today but I’m totally new to the codebase so we might have to iterate a few times

are there docs I can follow to test locally on my own? That might speed up the iteration process

<https://github.com/pulumi/pulumi-docker/pull/294>

Will get it reviewed tomorrow! Sorry first day back after vacation

Hey <@UDAP6PRRT> so I am looking at your PR right now...

ok, so the pulumiTypes are actually automated :confused: So any codegen changes will blog your changes away

I need to dig in and find out what is causing those to be generated as though types

ah, damn! My bad for not noticing that. Is there anything I can do to help support you?

glad to hear, I’d really like to get this fix out since it’s slowing down my CI pipelines a lot

<@UDAP6PRRT> so the good news here is that this is not autogenerated code