fix: add OC_USER and OC_EMAIL to dev-env .env.local

[patjlm]

Summary

• make dev-env now includes OC_USER and OC_EMAIL in the generated .env.local
• Fixes 401 errors when creating workspaces from the local frontend dev server (make dev COMPONENT=frontend)
• Aligns local dev setup with the kind overlay (frontend-test-patch.yaml) which already sets these vars

Root cause

The frontend proxy (buildForwardHeaders in auth.ts) uses OC_USER to set the X-Forwarded-User header. Without it, the backend's forwardedIdentityMiddleware cannot populate userID in the Gin context, and CreateProject fails with "no user subject found in token".

Test plan

• Run make kind-up LOCAL_IMAGES=true
• Run make dev-env and verify components/frontend/.env.local contains OC_USER and OC_EMAIL
• Run make dev COMPONENT=frontend
• Create a new workspace from localhost:3000 — should succeed (previously returned 401)

🤖 Generated with Claude Code

[coderabbitai]

📝 Walkthrough

Walkthrough

The Makefile's dev-env target now exports two additional OpenShift identity environment variables (OC_USER and OC_EMAIL) into the frontend .env.local configuration alongside the existing OC_TOKEN setup.

Changes

Cohort / File(s)	Summary
Build Configuration Makefile	Extended dev-env target to populate OC_USER (serviceaccount reference) and OC_EMAIL (test-user@vteam.local) in frontend environment file, complementing existing OC_TOKEN logic.

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format (fix: scope description) and accurately describes the main change: adding OC_USER and OC_EMAIL environment variables to dev-env configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Performance And Algorithmic Complexity	✅ Passed	Change adds two static string assignments (OC_USER, OC_EMAIL) to dev-env Makefile target with constant-time O(1) operations and no unbounded growth.
Security And Secret Handling	✅ Passed	PR introduces no security vulnerabilities. OC_USER and OC_EMAIL are non-sensitive hardcoded server-side values. OC_TOKEN uses secure pattern via K8s secret, not exposed client-side.
Kubernetes Resource Safety	✅ Passed	PR only modifies Makefile dev-env target with environment variables; no Kubernetes manifests or resource configurations present.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[patjlm]

Or I (and claude) may have missed some kind of setup 😉