Add python pub/sub docs

[pablomartinezbernardo]

What does this PR do? What is the motivation?

Add python pub/sub docs by extracting the content to a shortcode. Also, fix 2 issues (changing it in the shortcode, and therefore in the preexisting node docs):

1. Use --transport-topic for existing Pub/Sub topics

The previous Eventarc examples used:

--event-filters="type=google.cloud.pubsub.topic.v1.messagePublished"
--event-filters="topic=projects/my-project/topics/orders"

They now use:

--event-filters="type=google.cloud.pubsub.topic.v1.messagePublished"
--transport-topic=projects/my-project/topics/orders

The distinction is important:

• --transport-topic selects the Pub/Sub topic that transports messagePublished events.
• Google documents that if --transport-topic is omitted, Eventarc creates a transport topic. Therefore, using topic as an event filter does not bind the trigger to the existing orders topic.
• Google’s official Cloud Run example uses the same type event filter followed by --transport-topic=projects/PROJECT_ID/topics/TOPIC_ID.

Sources:

• Google Cloud CLI reference for gcloud eventarc triggers create (https://docs.cloud.google.com/sdk/gcloud/reference/eventarc/triggers/create)
• Google Cloud Pub/Sub triggers for Cloud Run (https://docs.cloud.google.com/run/docs/triggering/pubsub-triggers

2. Remove “Distributed tracing with Pub/Sub” from Cloud Run Jobs

Both parts of the section assumed a request-serving Cloud Run resource:

1. The direct subscription example configured an HTTP endpoint:

   --push-endpoint=https://order-processor-xyz.run.app/pubsub

2. The Eventarc Standard example configured:

   --destination-run-service=order-processor

Neither applies to a Cloud Run Job:

• Google explicitly states that a Cloud Run Job runs its tasks and exits; it does not listen for or serve requests. Consequently, it cannot receive Pub/Sub push deliveries at a run.app request endpoint. Cloud Run Jobs documentation (https://docs.cloud.google.com/run/docs/create-jobs)
• The Eventarc Standard CLI defines --destination-run-service as the name of a Cloud Run fully managed service. It is not a Cloud Run Job destination. Eventarc trigger CLI reference (https://docs.cloud.google.com/sdk/gcloud/reference/eventarc/triggers/create)
• Eventarc can execute Cloud Run Jobs through Eventarc Advanced, but that is a different integration. It requires a message bus, pipeline, enrollment, and a Cloud Run Admin API job-execution URI. It does not use the Standard --destination-run-service trigger shown in the removed section. Eventarc Advanced Cloud
  Run Jobs guide (https://docs.cloud.google.com/eventarc/advanced/docs/quickstarts/publish-events-cloud-run-job)

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/containers/in_container/nodejs
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/containers/in_container/python
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/containers/sidecar/nodejs
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/containers/sidecar/python
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/functions/nodejs
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/functions/python
• https://docs-staging.datadoghq.com/pmartinez/py-gcp-push-sub/serverless/google_cloud_run/jobs/nodejs

[maycmlee]

Just a small suggestion, otherwise looks good

[maycmlee]

@pablomartinezbernardo Thanks for using the general reuse shortcode! Left a comment about the links.

[maycmlee]

Thanls @pablomartinezbernardo! Just wanted to confirm one thing.

[maycmlee]

Just want to confirm that you didn't want to add the shortcode here.

[pablomartinezbernardo]

Correct, this is because of my "2. Remove “Distributed tracing with Pub/Sub” from Cloud Run Jobs" comment in the PR description: This should not have ever been included in cloud run jobs

[maycmlee]

Ah okay, thanks! Feel free to merge when ready!