gcp.container.getRegistryImage does not return image digest

[Ziinc]

What happened?

Image digest is not getting returned or exported.

Expected Behavior

Digest of the image should be exported

Steps to reproduce

const containerImage = gcp.container.getRegistryImage({
  name: 'my-container',
  project: "my-project",
  tag: 'latest',
})

export const containerImageDigest = containerImage.then(i=> i.digest)
export const containerImageId = containerImage.then(i=> i.id)
export const containerImageUrl = containerImage.then(i=> i.imageUrl)
export const containerImageName = containerImage.then(i=> i.name)

Output of pulumi about

» pulumi about
CLI          
Version      3.76.0
Go Version   go1.20.6
Go Compiler  gc

Plugins
NAME    VERSION
gcp     6.34.0
nodejs  unknown

Host     
OS       darwin
Version  13.2
Arch     arm64

This project is written in nodejs: executable='/Users/tzeyiing/.asdf/shims/node' version='v18.13.0'

Current Stack: supabase/logflare/staging

TYPE                                                   URN
pulumi:pulumi:Stack                                    urn:pulumi:staging::logflare::pulumi:pulumi:Stack::logflare-staging
pulumi:providers:gcp                                   urn:pulumi:staging::logflare::pulumi:providers:gcp::default_6_34_0
gcp:compute/healthCheck:HealthCheck                    urn:pulumi:staging::logflare::gcp:compute/healthCheck:HealthCheck::http-health-check-pulumi
gcp:compute/instanceTemplate:InstanceTemplate          urn:pulumi:staging::logflare::gcp:compute/instanceTemplate:InstanceTemplate::instance-template-pulumi
gcp:compute/instanceGroupManager:InstanceGroupManager  urn:pulumi:staging::logflare::gcp:compute/instanceGroupManager:InstanceGroupManager::logflare-cluster-pulumi
gcp:compute/backendService:BackendService              urn:pulumi:staging::logflare::gcp:compute/backendService:BackendService::pulumi-grpc-backend
gcp:compute/backendService:BackendService              urn:pulumi:staging::logflare::gcp:compute/backendService:BackendService::pulumi-backend
gcp:compute/uRLMap:URLMap                              urn:pulumi:staging::logflare::gcp:compute/uRLMap:URLMap::logflare-grpc-pulumi-lb
gcp:compute/uRLMap:URLMap                              urn:pulumi:staging::logflare::gcp:compute/uRLMap:URLMap::logflare-pulumi-lb
gcp:compute/targetHttpProxy:TargetHttpProxy            urn:pulumi:staging::logflare::gcp:compute/targetHttpProxy:TargetHttpProxy::http-proxy-pulumi
gcp:compute/targetHttpsProxy:TargetHttpsProxy          urn:pulumi:staging::logflare::gcp:compute/targetHttpsProxy:TargetHttpsProxy::https-proxy-pulumi
gcp:compute/globalForwardingRule:GlobalForwardingRule  urn:pulumi:staging::logflare::gcp:compute/globalForwardingRule:GlobalForwardingRule::http-frontend-pulumi
gcp:compute/globalForwardingRule:GlobalForwardingRule  urn:pulumi:staging::logflare::gcp:compute/globalForwardingRule:GlobalForwardingRule::https-frontend-pulumi
gcp:compute/targetHttpsProxy:TargetHttpsProxy          urn:pulumi:staging::logflare::gcp:compute/targetHttpsProxy:TargetHttpsProxy::grpc-proxy-pulumi
gcp:compute/globalForwardingRule:GlobalForwardingRule  urn:pulumi:staging::logflare::gcp:compute/globalForwardingRule:GlobalForwardingRule::https-grpc-frontend-pulumi

Found no pending operations associated with supabase/staging

Backend        
Name           pulumi.com
URL            https://app.pulumi.com/Ziinc
User           Ziinc
Organizations  Ziinc, supabase

Dependencies:
NAME            VERSION
@pulumi/gcp     6.34.0
@pulumi/pulumi  3.38.0
@types/node     14.18.26

Pulumi locates its logs in /var/folders/gq/2pmm0r1s2mq6w9bfqylc424r0000gn/T/ by default

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).

[rquitales]

Hello @Ziinc,

Thank you for bringing this issue to our attention. We've reviewed the matter, and it appears that this feature is currently a requested enhancement in the upstream Terraform provider. Rest assured, we will diligently monitor any updates from the upstream project and promptly incorporate the feature into our provider once it becomes available.

Your patience is greatly appreciated, and we'll make sure to keep you informed of any progress. If you have any further questions or concerns, please don't hesitate to reach out.