Cloud Run instrumentation fails: `dd_sls_ci` label value 'v4.1.2' violates GCP label format constraints

[CesarLanderos]

Bug description

When running datadog-ci cloud-run instrument with v4.1.2, the instrumentation fails with an INVALID_ARGUMENT error because the dd_sls_ci label contains periods, which violate GCP Cloud Run label format constraints.

Error message:

✖ Instrumenting service [service-name]
Error:  Failed to instrument service [service-name]: Error: 3 INVALID_ARGUMENT: labels: At least one label does not conform to GCP naming style. Label value 'v4.1.2' violates format constraints. The value can only contain lowercase letters, numeric characters, underscores and dashes. The value can be at most 63 characters long. International characters are allowed.

Error:  Uninstrumentation failed: Error: 3 INVALID_ARGUMENT: labels: At least one label does not conform to GCP naming style. Label value 'v4.1.2' violates format constraints. The value can only contain lowercase letters, numeric characters, underscores and dashes. The value can be at most 63 characters long. International characters are allowed.

The CLI attempts to add this label to the Cloud Run service:

"labels": {
  "dd_sls_ci": "v4.1.2",  # ❌ Periods violate GCP constraints
  "env": "XXX",
  "service": "XXX",
  "version": "XXX"
}

Root cause: GCP Cloud Run label values can only contain lowercase letters, numeric characters, underscores, and dashes. The version string v4.1.2 contains periods (.), which are not allowed.

Describe what you expected

The CLI should successfully instrument the Cloud Run service with GCP-compliant label values. The dd_sls_ci label should use a format like v4-1-2 (replacing periods with dashes or anything else) instead of v4.1.2.

Steps to reproduce the issue

1. Install datadog-ci v4.1.2:

npm install -g @datadog/datadog-ci@4.1.2

2. Run Cloud Run instrumentation:

datadog-ci cloud-run instrument \
  --project XXX \
  --service XXX \
  --region us-central1 \
  --env XXX \
  --version XXX

3. Observe the INVALID_ARGUMENT error

Note: This issue did not occur in v4.0.2 and earlier, which did not add the dd_sls_ci label.

Additional context

• OS version: macOS (Darwin 25.0.0)
• Node version: 24.5.0
• Package manager: npm
• datadog-ci version: v4.1.2
• GCP Project Type: Cloud Run (2nd gen / Cloud Functions)

Command

None

[ava-silver]

Thanks for the report! I'll get out a fix ASAP!

[ava-silver]

Since it's a Friday evening, we'll wait until Monday to release v4.1.3 with the fix -- in the meantime please stick to https://github.com/DataDog/datadog-ci/releases/tag/v4.0.2 which doesn't have the issue.

[ava-silver]

Version https://github.com/DataDog/datadog-ci/releases/tag/v4.1.3 has been released, which fixes this problem. Please upgrade the cloud run plugin to the latest to get the fix!

[sibblegp]

I found this and successfully instrumented my google cloud function, but the APM doesn't look right. It just says "GET" instead of the verb and the path. It's not very useful.

Is this standard for a cloud function or is something broken? If so, what? Thanks!

Only difference I can think of is the node environment its running in and it's not running in Typescript (It's a NestJS/express app) but Javascript.