Skip to content

feat: show a Compute enablement banner on the empty Workloads page - #233

Open
kevwilliams wants to merge 1 commit into
mainfrom
feat/compute-enablement-banner
Open

feat: show a Compute enablement banner on the empty Workloads page#233
kevwilliams wants to merge 1 commit into
mainfrom
feat/compute-enablement-banner

Conversation

@kevwilliams

@kevwilliams kevwilliams commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a banner to the Workloads page for projects without an Active compute ServiceEntitlement.

The banner's button creates the same ServiceEntitlement object (services.miloapis.com/v1alpha1, name compute, spec.serviceRef.name: compute) that datumctl's "Would you like to request access?" prompt creates.

The banner covers three states: not requested, pending approval, and rejected (with a "Request access again" button). State comes from status.phase.

The "Deploy a workload" and "List & inspect workloads" CLI cards stay visible in all states, since those datumctl commands request access on their own.

Extracted a shared Banner shell (icon, title, description, actions) used by both CliBanner and the new ComputeEnablementBanner.

Screenshot From 2026-08-17 13-51-59 Screenshot From 2026-08-17 13-52-05

Test plan

  • npm run typecheck in ui/consumer
  • npm run build in ui/consumer
  • Against a project with no compute ServiceEntitlement: confirm the banner and CLI cards render, and "Enable Compute" creates the entitlement and moves the banner to pending approval
  • Confirm the enabled-and-empty and enabled-with-workloads states still render as before

When a project doesn't have an Active `compute` ServiceEntitlement yet,
the Workloads page now shows a banner explaining that Compute needs to
be enabled, with a button that creates the same ServiceEntitlement
object datumctl's "Would you like to request access?" prompt does. The
"Deploy a workload" / "List & inspect workloads" CLI cards stay visible
either way, since those datumctl commands request access themselves.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant