CLI

confiqure diff

Show what confiqure push would upload, without uploading. Fetches the workspace registry and renders a side-by-side comparison.

Synopsis

$ confiqure diff

What it shows

The CLI scans your project for annotated classes, calls GET /api/{workspaceKey}/upload to fetch the live registry, and renders two diff sections:

• Annotated classes

  Classes the engine turns into live endpoints. These are the source of truth your end-users converse with — matched to the registry by class identity, marked CHANGED when the git SHA differs.

• Context files

  Supporting types reachable from your annotated classes (enums, value objects). The engine reads these for context but doesn't generate endpoints from them.

Example output

$ confiqure diff

Scanned 42 files; 3 annotated.
Backend registry: 3 classes.

Annotated classes (3 changes, 1 unchanged):
  ADDED    NotificationPreferences      src/main/java/.../NotificationPreferences.java  a1b2c3d
  CHANGED  ProfileSettings              src/main/java/.../ProfileSettings.java          e4f5a6b
  DELETED  LegacyConfig                 (was: src/main/java/.../LegacyConfig.java)

Context files:
  src/main/java/.../Channel.java

When to use it

• Before a release, to confirm you're shipping the right schema changes.
• In a PR check that should fail when uncommitted schema drift exists.
• To sanity-check that a refactor didn't accidentally orphan an annotated class.