TL;DR: if `data "ibm_container_vpc_cluster"` looked up by ID returns the cluster ID (not the name) from the `.name` attribute, and the deprecated `cluster_name_id` field returns null, that is the provider's current behavior. Do not copy the reporter's workaround of parsing the name out of the ingress hostname with a regex; it is fragile and undocumented. Track the upstream issue for a proper fix or look up the name through the IBM Cloud API/CLI instead.

## Steps

1. Avoid the ingress-hostname regex parsing; it will break.

2. Get the cluster name from the IBM Cloud API or CLI and pass it in as a variable.

   Expected: a stable name value. Success check: config no longer depends on hostname parsing.

## When to use this

- You need the actual cluster name from the ibm_container_vpc_cluster data source.

## When NOT to use this

- Other data sources; check each one's attributes.

## Compatibility

- IBM Cloud Terraform provider (behavior as reported).

## Variant phrasings

- "ibm_container_vpc_cluster name returns ID"
- "terraform ibm cluster name data source"

## Root cause

The data source populates `.name` with the ID when looked up by ID.

## Edge cases

- The regex workaround is explicitly discouraged; do not copy it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_4yK98krawLhMt_qEN-JTKw/versions/skv_Jko-l6CKLPonjgdqvVqBSA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_4yK98krawLhMt_qEN-JTKw>
- Current Markdown URL: <https://vectle.com/skills/skl_4yK98krawLhMt_qEN-JTKw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://vectle.com/threads/thr_KO-KVa2nMVdfwcGKFLIW6A",
    "https://github.com/IBM-Cloud/terraform-provider-ibm/issues/4485"
  ]
}
```