cnos workspace

cnos workspace

Use cnos workspace when one CNOS root needs to serve more than one app or package.

Enable workspace mode

If the repo started with a flat .cnos/ tree:

cnos workspace enable

CNOS moves:

• .cnos/values -> .cnos/workspaces/base/values
• .cnos/secrets -> .cnos/workspaces/base/secrets
• .cnos/env -> .cnos/workspaces/base/env
• .cnos/profiles -> .cnos/workspaces/base/profiles

and updates the root anchor to workspace: base.

Add a workspace

cnos workspace add travel --package-root apps/travel

If base exists, the new workspace automatically gets extends: [base].

Override that when needed:

cnos workspace add api --extends shared
cnos workspace add sandbox --extends none

List and remove

cnos workspace list
cnos workspace remove gallery

Scaffold wording

If your team prefers scaffold wording:

cnos workspace scaffold insights --package-root apps/insights --extends base

Detach and attach

cnos workspace detach --package-root apps/travel
cnos workspace attach --package-root apps/travel

Detach makes a child package independent. Attach imports it back into the parent workspace model.