Is the implementation of pulumi-docker considered idiomatic / "correct"? Specifically, that the resource constructors do actual work, including building images? In cloud-centric packages, all work is done in providers, once the Pulumi engine is called. But for Pulumi docker, work is being done in our Pulumi code, before the engine gets involved. As it currently stands, it's not possible to write unit tests with these resources.

As far as I know, we have some ongoing work to improve the Docker provider. What you are describing in the issue is a know behavior that we aim at changing in a future rework of that provider.

Can I bring the issue to the attention of a team member who'd be willing to mark it as in-progress or similar? I'd like to be able to update my clients who are affected by this.

My suggestion would be to detail your current situation in the github issue (no need for names) with as much details as possible, especially on the impact/pain this is causing. If you could add some context on any deadlines, that would be very helpful.

Okay