feat: make OpenCode the default DevSpaces IDE - #20
Conversation
Flip chart and existing-OpenShift defaults to OpenCode while keeping Continue as TYPE=continue.
Soft-skip ConfigMap assertions when those resources are absent for OpenCode.
Align README, IDE guide, existing-OpenShift docs, and deploy skill with the new default.
| opencodeBuild: | ||
| enabled: false | ||
| devspaces: | ||
| - name: code-workspace-1 |
There was a problem hiding this comment.
TYPE=continue silently deploys with wrong Langfuse user. user: dev-user1 is a hardcoded placeholder. The Makefile enforces DEV_USER only when TYPE=opencode; a developer running make devspace-deploy-existing-openshift DEV_NAMESPACE=foo TYPE=continue without DEV_USER will deploy successfully with dev-user1 as the Langfuse attribution user — no error, no warning.
Add the same guard to the Makefile for the continue path: @if [ "$(TYPE)" = "continue" ] && [ -z "$(DEV_USER)" ]; then echo "ERROR: DEV_USER is required for TYPE=continue. Pass DEV_USER="; exit 1; fi
There was a problem hiding this comment.
Fixed: DEV_USER is now required for both opencode and continue (no continue escape hatch). It always sets devspaces[0].user so Langfuse X-PCA-User and the edit RoleBinding match the real developer.
| N ?= 4 | ||
| DEV_USER ?= | ||
| TYPE ?= continue | ||
| TYPE ?= opencode |
There was a problem hiding this comment.
Invalid TYPE silently defaults to OpenCode.
Add a guard before the helm upgrade call:
@if [ "$(TYPE)" != "opencode" ] && [ "$(TYPE)" != "continue" ]; then echo "ERROR: TYPE must be opencode or continue"; exit 1; fi
There was a problem hiding this comment.
Fixed: TYPE must be opencode or continue; anything else errors.
There was a problem hiding this comment.
Continue/Roo tests skip on OpenCode workspaces but no OpenCode assertion exists. With OpenCode now the default, a freshly deployed cluster runs the entire devspace smoke suite and reports every test as SKIPPED — zero actual assertions pass. The suite gives false confidence on new installs.
There was a problem hiding this comment.
Fair point. Soft-skipping Continue/Roo ConfigMaps stays intentional (they aren’t created for OpenCode). Added always-on OpenCode checks that work with started: false: test_opencode_devworkspace_exists and test_opencode_web_password_secret.
There was a problem hiding this comment.
Gateway API-key tests skip on OpenCode workspaces with no replacement coverage. pca-ai-gw-apikey Secret is created for all workspace types, but no test asserts it exists or is non-empty on OpenCode workspaces. The gateway wiring goes fully untested for the new default path.
There was a problem hiding this comment.
Agreed on the wiring gap. Continue/Roo ConfigMap key checks still soft-skip on OpenCode. OpenCode RHCL/key wiring + chat now run on any-phase DevWorkspace CRs (not only Running), so fresh started: false installs are covered.
2 participants
Summary
TYPE=opencode; Continue viaTYPE=continue)Commits