Skip to content

chore: deploy-audit cleanup (drop stale Docker scaffolding, pin deadcode)#26

Merged
Patel230 merged 1 commit into
mainfrom
fix/deploy-audit-cleanup
Jun 10, 2026
Merged

chore: deploy-audit cleanup (drop stale Docker scaffolding, pin deadcode)#26
Patel230 merged 1 commit into
mainfrom
fix/deploy-audit-cleanup

Conversation

@Patel230

Copy link
Copy Markdown
Contributor

Why

A deploy-readiness audit across the hawk-eco set surfaced two pieces of stale Docker scaffolding in this repo. eyrie is a Go library (no cmd/, no package main outside examples/, Makefile build target literally says "eyrie is a library consumed by hawk; no standalone binary"), so a deploy/docker/docker-compose.yml plus .dockerignore that referenced a non-existent Dockerfile were misleading and broken (docker compose build would fail on first invocation).

What changed

Removed

  • deploy/docker/docker-compose.ymlbuild.dockerfile: Dockerfile with context ../../. No Dockerfile exists anywhere in the repo (verified via find -name 'Dockerfile*'). Consumers who want eyrie as an HTTP service embed internal/api.Server from their own daemon (hawk does this).
  • deploy/ — directory deleted entirely (was empty after the compose file went away).
  • .dockerignore — vestigial; listed Dockerfile, docs/, deploy/, api/ — Dockerfile/deploy were absent, and docs/api/ are real source dirs that must not be excluded from any future build context.

Pinned

  • .github/workflows/ci.ymldeadcode pinned to v0.30.0 (was @latest). Matches hawk's pin and gives reproducible CI.

Validation

All run locally on Go 1.26.4 (matches go.mod):

Check Result
go build ./... clean
go vet ./... clean
gofumpt -l . / goimports -l . clean
golangci-lint run --timeout=5m 0 issues
go test ./... -short all pass
govulncheck ./... no vulnerabilities

Risk

Low. No *.go source files modified.

Follow-ups (separate PRs)

The audit also found similar stale scaffolding in tok, yaad, and hawk — those will get their own PRs. tok PR: GrayCodeAI/tok#56.

…code

eyrie is a library (no `cmd/`, no `package main` outside `examples/`, and
the Makefile build target literally documents this). The repo carried a
`deploy/docker/docker-compose.yml` that built a `Dockerfile` that never
existed, plus a `.dockerignore` listing patterns for the absent
Dockerfile. Both are removed.

Removed
-------
- deploy/docker/docker-compose.yml — `dockerfile: Dockerfile` with context
  `../../`; no Dockerfile is present. `docker compose build` fails on
  first invocation. eyrie ships as a Go module via `go get`; consumers
  embed its HTTP `api.Server` if they want to expose it.
- deploy/ — directory deleted entirely (was empty after the compose file
  went away).
- .dockerignore — vestigial; listed Dockerfile/docs/deploy/api which were
  either absent or are real source dirs that must NOT be excluded.

Pinned
------
- .github/workflows/ci.yml: deadcode pinned to v0.30.0 (was `@latest`).
  Matches hawk's pin and gives reproducible CI.

Validation
----------
- go build ./... — clean
- go vet ./... — clean
- gofumpt -l . / goimports -l . — clean
- golangci-lint run --timeout=5m — 0 issues
- go test ./... -short — all pass
- govulncheck ./... — no vulnerabilities

@Patel230 Patel230 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-review (cannot approve own PR): no .go source touched; only deletes a stale docker-compose + .dockerignore and pins deadcode. All 15 CI checks green. Merging.

@Patel230

Copy link
Copy Markdown
Contributor Author

Self-review: no .go source touched; only deletes a stale docker-compose + .dockerignore and pins deadcode. All 15 CI checks green. Merging.

@Patel230 Patel230 merged commit cc782e4 into main Jun 10, 2026
15 checks passed
@Patel230 Patel230 deleted the fix/deploy-audit-cleanup branch June 10, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant