Skip to content

[SPEC] Remove Dagger from the opinionated platform stack. Dagger's footprint is now low-ROI and partly redundant: the one CI step (dagger call pre-commit-tf) duplicates the native antonbabenko pre-commit-terraform hooks already in .pre-commit-config.yaml, while the heavyweight parts — the in-cluster dagger-engine deployment (tooling/base/dagger-engine/) and a dedicated dagger GHA runner scale set (tooling/base/gha-runners/dagger-scale-set-helmrelease.yaml) — carry real maintenance surface (network policies, PDB, upgrades, a runner pool) for that thin benefit. SPEC-007 already moved manifest validation off its Dagger function onto a plain script (validate-manifests.sh). Scope: inventory every Dagger touchpoint (CI workflows, in-cluster engine, runner scale set, polaris/kustomization refs), confirm the pre-commit redundancy, define the teardown order, and decide whether to keep a minimal example for the blog's Dagger intro post. Rationale is low-ROI/redundancy, explicitly NOT trendiness or AI. #1595

Description

@Smana

Summary

Remove Dagger from the opinionated platform stack. Dagger's footprint is now low-ROI and partly redundant: the one CI step (dagger call pre-commit-tf) duplicates the native antonbabenko pre-commit-terraform hooks already in .pre-commit-config.yaml, while the heavyweight parts — the in-cluster dagger-engine deployment (tooling/base/dagger-engine/) and a dedicated dagger GHA runner scale set (tooling/base/gha-runners/dagger-scale-set-helmrelease.yaml) — carry real maintenance surface (network policies, PDB, upgrades, a runner pool) for that thin benefit. SPEC-007 already moved manifest validation off its Dagger function onto a plain script (validate-manifests.sh). Scope: inventory every Dagger touchpoint (CI workflows, in-cluster engine, runner scale set, polaris/kustomization refs), confirm the pre-commit redundancy, define the teardown order, and decide whether to keep a minimal example for the blog's Dagger intro post. Rationale is low-ROI/redundancy, explicitly NOT trendiness or AI.

Type

platform

Spec Directory

docs/specs/009-remove-dagger-opinionated-platform/

The spec is a 3-file directory:

  • spec.md — contract (WHAT + why)
  • plan.md — design, tasks, 4-persona review checklist
  • clarifications.md — append-only decisions log

Spec anchor for discussion. See docs/specs/009-remove-dagger-opinionated-platform/ for the full specification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    specFormal specification for non-trivial changesspec:draftSpec in draft state

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions