Skip to content

coder-ddev: Spring 2026 improvement sprint #83

@rfay

Description

@rfay

Tracking issue for the Spring 2026 coder-ddev improvement sprint, now that a Hetzner staging server is coming online.

Phase 1: Quick Wins (no staging required)

Small, safe, additive changes — image rebuild + template push to production.

Phase 2: Staging Server + Template Test Workflow (#77)

Two parallel tracks:

A. Template testing via --activate false on production — push a new template version without activating it, create a named test workspace from that version, validate, then promote. Add ACTIVATE ?= true variable to Makefile to make this easy.

B. Hetzner staging server — needed for image changes, storage path changes, auth config, and anything that carries risk to existing workspaces.

Phase 3: Template / Logic Fixes

Use --activate false workflow or staging to validate before promoting.

Phase 4: Auth Hardening

Test on staging first, then apply to production.

Phase 5: Automated Tests

The enabler for safe future iteration. Needs staging server as E2E target.

  • Add automated tests #71 Add automated tests — terraform validate/fmt on PRs + E2E workspace smoke test against staging

Phase 6: Refactor

Requires test coverage from Phase 5 so regressions are caught automatically.

Phase 7: New Features

Lowest urgency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions