Motivation
Platforms built on kcp usually have a UI. Agents should be able to hand the user a link to the resource they are talking about, but the URL scheme is platform knowledge the generic server cannot have.
Proposal
An optional flag:
--resource-url-template=https://ui.example.com/w/{workspace}/r/{group}/{version}/{resource}/{namespace}/{name}
When set, list and get responses include a url field per item, rendered from the template. Unset means no change to responses. The server stays platform-agnostic, each deployment injects its own scheme through chart values.
Notes
Template variables should cover workspace (name and cluster ID), group, version, resource, namespace and name. Cluster-scoped resources render without the namespace segment.
Motivation
Platforms built on kcp usually have a UI. Agents should be able to hand the user a link to the resource they are talking about, but the URL scheme is platform knowledge the generic server cannot have.
Proposal
An optional flag:
When set, list and get responses include a
urlfield per item, rendered from the template. Unset means no change to responses. The server stays platform-agnostic, each deployment injects its own scheme through chart values.Notes
Template variables should cover workspace (name and cluster ID), group, version, resource, namespace and name. Cluster-scoped resources render without the namespace segment.