The GitHub Actions job "Backport Checks" on 
texera.git/feat/admin-cu-list-endpoint has succeeded.
Run started by GitHub user kunwp1 (triggered by kunwp1).

Head commit for run:
bec99f2e5091e2c84741f840e86fca4ab6697bd9 / Kunwoo Park <[email protected]>
feat(computing-unit-managing-service): add admin endpoint to list all computing 
units

Add an ADMIN-only GET /computing-unit/admin/list that returns every
non-terminated computing unit across all users, backing the admin Computing
Units dashboard.

- AdminComputingUnitResource filters active units in SQL (excludes rows with a
  non-null terminate_time), reconciles vanished pods via the shared
  ComputingUnitHelpers, and assembles rows with each owner's name/avatar. The
  Kubernetes round trips stay outside the transaction so a pooled connection is
  not held across them; only the batched retire write is wrapped.
- accessPrivilege is reported as WRITE for admin rows; isOwner reflects whether
  the requesting admin owns the unit. The scaladoc records that the mutating
  endpoints have no ADMIN bypass yet, so a client must not present these rows as
  writable until they do.
- Register the resource in ComputingUnitManagingService and extend the startup
  access-control coverage check to include it.
- Nested under /computing-unit rather than /admin/<domain> because the gateway
  only routes /api/computing-unit to this service; documented at the class.

Builds on the shared listing helpers from #6853.

Tests: AdminComputingUnitResourceSpec drives listAllComputingUnits end-to-end
over the embedded DB (terminated rows excluded, WRITE access, isOwner, empty
table, and a caller owning none of the units); 
ComputingUnitManagingServiceRunSpec
boots run() and verifies the admin resource plus the auth features that make
@RolesAllowed enforceable are registered, closing the pool afterwards (DB-gated:
connects only when Postgres is reachable, cancels otherwise).

Generated-by: Claude Code, Claude Opus 4.8

Report URL: https://github.com/apache/texera/actions/runs/30851522873

With regards,
GitHub Actions via GitBox

Reply via email to