Surface an error when the CRD schema cannot be fetched #576

Merged

tobru merged 1 commit from surface-crd-schema-fetch-error into main

2026-06-26 12:52:52 +00:00

tobru commented

2026-06-26 12:52:26 +00:00

Owner

When a control plane's CRD schema fetch fails (e.g. expired cluster credentials returning 401), both the expert and custom form classes are None. The create/update templates gated the form card on the forms being present, so the whole service form silently vanished with no error in the browser or the server log.

tobru added the

UI/UX

label

2026-06-26 12:52:26 +00:00

tobru added 1 commit

2026-06-26 12:52:27 +00:00

Surface an error when the CRD schema cannot be fetched

Tests / test (push) Successful in 1m23s

Details

8b391a1e06

When a control plane's CRD schema fetch fails (e.g. expired cluster
credentials returning 401), both the expert and custom form classes are
None. The create/update templates gated the form card on the forms being
present, so the whole service form silently vanished with no error in the
browser or the server log.

- resource_definition: log a warning instead of swallowing the
  ApiException / transport error, so failures are visible in the log
- create and update views: set form_error when a control plane is
  selected but its resource_schema is None
- create and update templates: render the error card when form_error is
  set even though no form could be built
- tests: cover the rendered error and the logged warning

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

tobru merged commit c6cefc1103 into main

2026-06-26 12:52:52 +00:00

tobru deleted branch surface-crd-schema-fetch-error

2026-06-26 12:52:52 +00:00

tobru referenced this pull request from a commit

2026-06-26 12:52:53 +00:00

Merge pull request 'Surface an error when the CRD schema cannot be fetched' (#576) from surface-crd-schema-fetch-error into main