Stage² for VS Code

Connect VS Code to Stage², where teams run engineering workflows in the cloud. Browse projects, move data files in and out, and publish a containerized block of work (an Operation) so colleagues can use it in a workflow. With git, the extension ties each publish to your repo so the Operation running in a workflow can be traced back to the code that built it.

If Stage² is new to you, the Stage² docs explain workflows, teams, and Operations. This extension works locally on your machine: Docker builds the image and pushes it to Stage²'s registry; Stage² keeps the definition and runs it when a workflow calls for it.

Features

Stage² Explorer
- After sign-in, browse organization → integration (project) → operations and assets in a tree.
Assets
- Upload a file to Stage² or download files from the tree (inputs, results, shared datasets).
Build & Push Operation
- Right-click a folder that contains a Dockerfile.
- Three-step wizard: operation interface, Docker settings, then build, register, and push.
Linked folders
- A successful push updates local operation.json (project link, revision info, optional git source_ref).
- Repeat pushes count as revisions on the same Operation in that project.
Source control
- Optional commit before push, source comparison in the Build & Push wizard, and git source_ref saved on disk and synced to Stage² (by default) so operation revisions trace back to commits.
Sign-in
- Stage² email and password; tokens live in VS Code Secret Storage. No login dialog at startup.

Experimental: Foundry templates (stage2.foundry.enabled) are off by default and require a local Foundry service.

Requirements

A Stage² account
Docker on your PATH (or stage2.buildPush.dockerPath ).
(recommended) Git for commit prompts, source comparison, and source_ref (or stage2.buildPush.gitPath). Publish works without git; source tracking is limited.

Docker must run on the same machine as VS Code. On Windows, the extension uses Docker from your Windows PATH; it does not call Docker inside WSL unless you set PATH that way.

Getting started

Install the extension and open the Stage² icon in the activity bar.
Sign in to Stage² from the Explorer welcome link or the view title.
Refresh the Explorer to load/reload your organization and projects.
Build & Push: open a folder with Dockerfile and operation.json (or pick org/project in the wizard for an unlinked folder). Right-click the folder in File Explorer → Stage² Build & Push Operation.

Settings

Setting	Purpose
`stage2.baseUrl`	Stage² API base URL (default: production). Changing it signs you out.
`stage2.webClientUrl`	Web app URL for Open in Stage² (not the API).
`stage2.buildPush.syncSourceRefToStage2`	After push, send local `source_ref` to Stage² (default: on).
`stage2.buildPush.dockerPath` / `stage2.buildPush.gitPath`	Full paths when `docker` / `git` are not on PATH.
`stage2.debug.http`	Log API traffic to the Stage² HTTP output channel.
`stage2.foundry.enabled`	Show Foundry view (reload required).

Known limitations

You cannot pull an operation definition from Stage² in the UI. The wizard reads local operation.json first, then Stage² when the local file is thin.
Source comparison does not run git fetch. Commits missing from your clone show as unavailable, with a link to your host when possible.
Foundry, when enabled, expects a separate local service (not bundled with this extension).

Support

Use your usual SpatialOne / Stage² support channel. Platform help: docs.spatial-one.com.

Release notes

0.0.1 Initial release: Explorer, assets, Build & Push wizard, sign-in/out, linked operation.json workflow.