[Bug]: displayName is ignored on log-based metric

[shmuelarditi]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

logging.gcp.upbound.io/Metric/v1beta2

Resource MRs required to reproduce the bug

No response

Steps to Reproduce

Can be reproduced by deploying the example, or your own log based metric.

Deploy this:

apiVersion: logging.gcp.upbound.io/v1beta2
kind: Metric
metadata:
  annotations:
    meta.upbound.io/example-id: logging/v1beta2/metric
  labels:
    testing.upbound.io/example-name: logging_metric
  name: logging-metric
spec:
  forProvider:
    bucketOptions:
      linearBuckets:
        numFiniteBuckets: 3
        offset: 1
        width: 1
    filter: resource.type=gae_app AND severity>=ERROR
    labelExtractors:
      mass: EXTRACT(jsonPayload.request)
      sku: EXTRACT(jsonPayload.id)
    metricDescriptor:
      displayName: My metric
      labels:
      - description: amount of matter
        key: mass
        valueType: STRING
      - description: Identifying number for item
        key: sku
        valueType: INT64
      metricKind: DELTA
      unit: "1"
      valueType: DISTRIBUTION
    valueExtractor: EXTRACT(jsonPayload.request)

What happened?

When creating the log based metric in GCP, it uses the metadata.name field as the name in the UI
instead of the displayName..

Relevant Error Output Snippet

No response

Crossplane Version

1.17.0

Provider Version

1.8.3

Kubernetes Version

v1.30.5

Kubernetes Distribution

GKE

Additional Info

No response

[mergenci]

Reported behavior is the expected behavior. According to Terraform documentation display_name is not the resource name or resource ID, but a description to help human workflows.