Hi, we are experiencing a bit of a weird issue currently: We have a couple of cloudrunv2 Services, that are defined with

launch_stage="BETA"

cr2.Service(
    name,
    project=project,
    ...,
    launch_stage="BETA",
    ...,
)

but somehow pulumi up doesn't sync that correctly, because updating works, but when running a

pulumi up

a second time it still reports the old value set in the stack as

GA

Could you try doing a

pulumi refresh

, and see what diffs are reported

Pulumi refresh reports no diffs in any of the cloudrun services at all. And in the Dashboard Pulumi Webinterface in the Resource views it says

launchStage

is set to

GA

- even though its not

According to the rest api docs, if you specify beta, it'll change to GA if there isn't currently a beta available. Are there definitely beta stages for CloudRun atm?

We are making use of direct VPC egress: https://cloud.google.com/run/docs/configuring/vpc-direct-vpc In the docs there it does say that this is still classified as a Pre-GA feature.

Haha, yeah Google docs can be awkward to follow, especially when they don't provide api/tf references. The cli wraps up a lot of calls

Hmm, I removed

launch_stage="BETA"

now, running pulumi up this time says no changes, so that seems to be the current state of our system anyways 🙂 And checking on the cloud run docs page: https://cloud.google.com/run?hl=en The last highlight entry in "Features" is Direct VPC egress - so I guess this feature became GA in the meantime, and somehow our cloudrun services as well 😄 Tests show our system (including VPC egress) is still working fine.