No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

:wave: What are you trying to do? Maybe you can share some more information to make it easier for me to help out :slightly_smiling_face:

I am actually looking for this <https://github.com/GoogleCloudPlatform/terraform-google-cloud-run/issues/23>

cloud run supports url pinning for an exact revision.

but I can not achieve this with neither terraform nor pulumi.

The yml in service spec looks like this:

```  traffic:
  - percent: 100
    latestRevision: true
  - revisionName: hello-00001-wik
    tag: v1-0-0
  - revisionName: hello-00001-wik
    tag: v1-0-0-beta
  - revisionName: hello-00004-juk
    tag: v2-0-0
  - revisionName: hello-00004-juk
    tag: v2-0-0-beta```

So, the revision tag is configurable via yml. But not configurable via pulumi or terraform

found this exact issue on terraform <https://github.com/hashicorp/terraform-provider-google/issues/10341>

This is probably a nice use-case for the native Google provider. AFAIK, this is supported in this. Mind you: the native provider is currently in developer preview, so there be dragons. However, you can combine it with the current version anyway.

<https://github.com/pulumi/pulumi-google-native/>

That's nice. But the native provider breaks a lot of thing and it doesn't properly follow the knative yml schema as well. So, few example would be better as the original provider has. Thanks for letting me know about this provider.

AFAIK, It should be fully compliant with Google's API schema. The native provider is automatically generated, so there should be great/good coverage. I would recommend that you still use the current Google provider for most of your application, and only use the native provider for this particular resource.

They live well together :slightly_smiling_face: I've used <https://github.com/ayrorg/infra/blob/main/components/pubsub-service.ts|them together> for quite some time now.