Add CI/CD workflow with release versioning and GitOps frontend/backend deployments

[Copilot]

Adds a GitHub Actions pipeline to test, build, and push Docker images to GHCR, plus the missing frontend Kubernetes deployment. On release, Docker images are tagged with the release version and GitOps manifests are automatically updated via kustomize.

CI/CD Workflow (.github/workflows/ci.yml)

• test-backend: dotnet build + test (unit & integration)
• test-frontend: npm run build (vue-tsc type-check + vite build)
• build-and-push (main branch push or release, after tests pass): builds and pushes two images to ghcr.io:
  • ghcr.io/jwraats/wizard-rpg-api (backend)
  • ghcr.io/jwraats/wizard-rpg-frontend (frontend)
  • Tagged with latest + git SHA on push to main; additionally tagged with the release version (e.g., v1.0.0) on release
• update-gitops (release only): installs kustomize, runs kustomize edit set image to update both image tags in kustomization.yaml, and commits/pushes to main so ArgoCD auto-syncs the new version

GitOps Updates

• deployment.yaml: image → ghcr.io/jwraats/wizard-rpg-api:latest (overridden by kustomize images transformer on release)
• New frontend-deployment.yaml: nginx container with ConfigMap volume mount, health probes, resource limits
• New frontend-service.yaml: ClusterIP on port 80
• New frontend-nginx-configmap.yaml: nginx config that proxies /api/ and /hubs/ to the wizard-rpg backend service
• ingress.yaml: routes to wizard-rpg-frontend (frontend proxies API traffic to backend)
• kustomization.yaml: includes new frontend resources; images transformer is auto-updated with version tags on release

Request flow

Ingress → wizard-rpg-frontend (nginx:80) → static SPA
                                          → /api/  → wizard-rpg:80 (backend:8080)
                                          → /hubs/ → wizard-rpg:80 (backend:8080)

Integration test fix

Fixed 6 failing integration tests caused by Guid.NewGuid() being evaluated inside the AddDbContext options lambda, which created a separate in-memory database per HTTP request. Moved the guid evaluation outside the lambda so all requests within a test share the same database.

Validated with kustomize build — all manifests render correctly with proper label isolation between frontend and backend selectors.

[jwraats]

Would like to use version tags. (so on release)

[Copilot]

Updated in 9a64245. The workflow now triggers on release: [published] and tags Docker images with the release tag name (e.g., v1.0.0). The base deployment keeps :latest as the default, but the update-gitops job uses kustomize edit set image to add an images transformer to kustomization.yaml that overrides the tag with the release version.

[jwraats]

Version tags.

[Copilot]

Same as backend — on release, the frontend image gets tagged with the version and kustomize overrides the tag via the images transformer in kustomization.yaml. See 9a64245.

[jwraats]

Something with pushing the version tag to the gitops when the docker image is pushed maybe with kustomize?

[Copilot]

Added an update-gitops job in 9a64245. On release, after images are pushed, it checks out main, runs kustomize edit set image to set both image tags to the release version in kustomization.yaml, then commits and pushes. ArgoCD will pick up the change automatically.

[jwraats]

@copilot Resolve the PR comments

[Copilot]

@copilot Resolve the PR comments

All three comments addressed in 9a64245. Also fixed the 6 failing integration tests — the root cause was Guid.NewGuid() inside the AddDbContext options lambda, which created a new in-memory database per HTTP request instead of sharing one across the test. All 10 tests pass now.