Skip to content

[Applications] Add read-only environment-filtered application navigation #115

Open

Description

@mohit-nagaraj

Context

Parent: #112
Blocked by: #113 and #114

Core supports environment-scoped application identities that can exist as
drafts without a connected cluster. UI has no read-only application navigation,
so these records are invisible and users must continue treating legacy
workflows as the only application concept.

Outcome

For the active workspace, a user can browse applications, filter them by
environment, and distinguish desired draft metadata from live deployment state.

Scope

  • Add an Applications navigation entry and a read-only applications page.
  • Require a valid active workspace before loading workspace-scoped data.
  • Load the workspace's environments and non-archived applications.
  • Filter applications through Core's environmentId query parameter rather
    than filtering an incomplete client-side page.
  • Support the API's next cursor with a bounded Load more action when present.
  • Show application name, environment, draft/archive status represented by the
    response, and updated time without inventing health or deployment state.
  • Provide separate loading, no-workspace, no-environment, no-application,
    request-error, and retry states.
  • Add focused page tests for the primary and failure paths.

Out Of Scope

  • Application create, edit, archive, detail, deployment, or import flows.
  • Mapping legacy workflows into applications.
  • Artifact, release, plan, approval, cost, or live health views.
  • Client-side filtering across incomplete cursor pages.
  • Core changes or a new backend aggregation endpoint.

Acceptance Criteria

  • No application request is sent before an active workspace exists.
  • Changing environment requests the matching server-side filter.
  • Archived applications remain excluded by default.
  • Pagination appends without duplicating records.
  • Draft metadata is never labelled deployed, running, healthy, or live.
  • Loading, empty, failure, and retry states are independently testable.
  • Keyboard and mobile navigation remain usable.

Verification

  • Run focused Vitest and Testing Library tests.
  • Run npm run type-check.
  • Run the relevant lint command.
  • Include desktop and mobile screenshots in the PR.

Dependencies

Complete #113 and #114 first.

Documentation And Observability

Add a short user-facing note only if needed to explain that applications are
desired metadata and are not proof of a deployment. Do not expose raw
authorization or database errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiREST endpointsarea/testingTesting, quality assurance, validationarea/uiNext.js frontend (components, pages, styling)good first issueGood for newcomerskind/integrationConnecting frontend with backendpriority/highsize/sSmall task (0.5 day)sprint/nextNext sprint planned items

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions