Open losisin opened 11 months ago
Thank you for reporting this issue and I am sorry you are affected!
The ticket you mention says the user got their scenario to work on v6.49.0, does this version work for you as well (in which case we have a regression here?).
I'm suspecting https://github.com/pulumi/pulumi-terraform-bridge/issues/1342 might be implicated here as we're possibly truncating large "numbers" somewhere in the translation between Pulumi and TF.
@t0yv0 the ticket I mentioned says the user couldn't reference the output at all judging by the error:
E AttributeError: 'BackendService' object has no attribute 'generated_id'
the comment however, makes me think that this was issue since v6.49.0. I took the hint from the last 3 digits posted from output 9033009296946491000
which is similar to mine.
What happened?
When importing
gcp:compute/backendService:BackendService
there is wrong value forgeneratedId
. I need this value to be correct because I'm using it as env var for cloudrun service. It is required by jitaccess. This was working fine with terraform (that's how it was initially created). After import, last 4 digits are replaced with0000
. My guess is that it could be connected to this comment hereExample
pulumi import 'gcp:compute/backendService:BackendService' default projects/XXXXXXXXXXXX/global/backendServices/jitaccess-backend
Output of
pulumi about
Additional context
I verified both terraform state and output from
gcloud compute backend-services describe jitaccess-backend --global
and the value there is as it should.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).