ComputePlan already stored distinct request/limit fields and everything
downstream applied them independently, but the catalog ingest path
collapsed requests to limits and the update branch clobbered cpu_requests
with cpu_limits.

Add optional, nullable vcpus_requests/ram_gib_requests to
ComputePlanCatalogEntry. The sync parses the optional payload keys and
resolves the fallback (requests ?? limit) when producing ComputePlan,
applying all four fields independently. Surface the new fields in the
catalog admin.

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

Lock catalog-managed admin fields read-only

Tests / test (push) Successful in 1m7s

Details

ea736492c3

ComputePlan and ComputePlanAssignment had no read-only fields, so an
operator could edit values that sync_plan_catalog overwrites on the next
run. Mark the synced fields read-only: ComputePlan name and CPU/memory
fields, and ComputePlanAssignment is_active (also in the inline). Local
fields (description, is_active, sort_order, proposed_storage_gib) stay
editable. Add a guard test.

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

tobru changed title from ~~Managed Resource Request via Catalog API~~ to Manage Resource Request via Catalog API

2026-06-23 11:08:50 +00:00

tobru merged commit 6c21446935 into main

2026-06-25 08:08:45 +00:00

tobru deleted branch compute-requests-limits

2026-06-25 08:08:46 +00:00

tobru referenced this pull request from a commit

2026-06-25 08:08:47 +00:00

Merge pull request 'Manage Resource Request via Catalog API' (#570) from compute-requests-limits into main