Revert the earlier typo that changed the resourceTypes entry from
`buckets.storage.gcp.upbound.io` to `bucket.storage.gcp.upbound.io`
under the mistaken rationale of "consistency with preferred API
version". Kubernetes resource type specs in generation rules use the
API plural name (as reported by `kubectl api-resources`), which for
this CRD is `buckets`.
Confirmed against the live cluster:
kubectl api-resources --api-group=storage.gcp.upbound.io
NAME=buckets NAMESPACED=false KIND=Bucket
Symptom of the typo (from workspace-builder logs, image
`806-merge-343c86e3`):
Trying custom resource bucket.storage.gcp.upbound.io
Error scanning for custom resource instances; error: (403)
The 403 was misleading — it isn't an RBAC problem (the ClusterRole
correctly grants get/list/watch on `buckets`); it's the API server
rejecting a call for a resource type that doesn't exist. The
scope-aware discovery from runwhen-local PR #806 is working; it
just had the wrong plural to look up.
Co-authored-by: Cursor <cursoragent@cursor.com>
stewartshea
fe0946a146