Closed guineveresaenger closed 1 year ago
Is there a work-around for this? I tried downgrading to v3.75.0 without luck.
@nstires-ctgx was this working for you at some earlier version, either of pulumi-docker
or pulumi
?
I looked at the stack history, looks like last update that worked was on 3.76.0. The resource types that were failing with the corresponding outputs are as follows:
type: gcp:cloudfunctions:Function
output: httpsTriggerUrl
type: gcp:vpcaccess:Connector
output: id
It seems that it's failing during preview as I can bypass the errors with --skip-preview
.
What happened?
A user reported https://github.com/pulumi/pulumi-docker/issues/685.
In summary, the user was attempting to use
baseImageName
, a resource output property ondocker.Image
, as theimage
field ondocker.Container
. Initial creation works fine; but when updating the Image resource, the Container.Image field is set tonull
.We have verified that this behavior does not occur when using the NodeJS runtime.
When reproducing the issue on Docker, the GRPC logs for Check() which is where the error occurs look like this:
Expected Behavior
The dependent resource (
docker.Container
) should have access todocker.Image
's output field.Steps to reproduce
The user provided a reproduction of this issue.
Output of
pulumi about
n/a - yaml does not tell you the current version. Using latest pulumi.
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).