Workspace Composer
The Workspace Composer lets you edit workspace.poly and secrets.poly directly in the Polycrate Web UI for workspaces without Git sync: when to use it, its features and how it differs from GitOps workspaces.
Workspace Composer
The Workspace Composer allows direct editing of workspace.poly and
secrets.poly in the Web UI — without a Git checkout — for workspaces with
git_sync_enabled=False.
When to Use It?
| Mode | Behavior |
|---|---|
git_sync_enabled=False |
Composer: edit, validate, save |
git_sync_enabled=True |
Git remains the source of truth; content comes via GitLab Files / sync |
With Git sync, the API imports workspace content via the GitLab Repository Files API at the commit SHA (no more CLI snapshot in the reconcile path). The Composer does not replace this path.
Features
workspace.poly— full-featured editor with validation and saving- CatalogueApp sidebar — conveniently add blocks
secrets.poly— Monaco editor with auto-save and validation for secrets/API keys- Meta fields on the workspace:
description,purpose,urls,owner,version/app_version, optional SSH key credential
Scope
- Not a replacement for GitOps workspaces
- Component auto-discovery from block
from:patterns is dropped; components are no longer pulled in automatically from the workspace file - Secrets do not belong in Git — the Composer stores them encrypted on the API side