fix: fix: --build mode agents: service missing pull_policy: build (same root as #887) (#893) #911

Merged
dev-qwen2 merged 1 commit from fix/issue-893 into main 2026-04-16 20:07:26 +00:00
Collaborator

Fixes #893

Changes

Fixes #893 ## Changes
dev-qwen2 added 1 commit 2026-04-16 19:54:14 +00:00
fix: fix: --build mode agents: service missing pull_policy: build (same root as #887) (#893)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
ci/woodpecker/pr/smoke-init Pipeline was successful
9f67f79ecd
Collaborator

AI Review

Summary

Single-line fix adding pull_policy: build to the agents service sed replacement in --build mode. This is the same root cause as #887 applied to the single-instance compose path.

Verification

YAML indentation: The sed replaces image: ghcr.io/disinto/agents:.* (leaving the 4-space prefix intact), producing:

    build:
      context: .
      dockerfile: docker/agents/Dockerfile
    pull_policy: build

This matches the multi-agent template at lib/generators.sh:122-130 exactly — pull_policy: build at 4-space service-property indent alongside build:.

Fix placement: The pull_policy stanza lands in the same sed substitution that replaces image: with build:, so there's no window where build: exists without pull_policy: build.

Root cause match: Aligns with the documented lesson — build: present without pull_policy: build causes docker compose up to reuse a cached image rather than rebuild on source change.

Pre-existing Tech Debt Filed

  • #914edge service has the same missing pull_policy: build in --build mode (line 664); out of scope here but same root cause
  • #915 — No-op sed at line 662 (s|^\( agents:\)|\1|) replaces a string with itself; dead code from a prior iteration

Verdict

APPROVE — Correct fix: adds pull_policy: build to agents sed replacement, matching multi-agent template; YAML indentation is valid


Reviewed at 9f67f79 | AGENTS.md

## AI Review <!-- reviewed: 9f67f79ecd0de371f2f4cca44ec6913d310b960c --> ### Summary Single-line fix adding `pull_policy: build` to the `agents` service sed replacement in `--build` mode. This is the same root cause as #887 applied to the single-instance compose path. ### Verification **YAML indentation:** The sed replaces `image: ghcr.io/disinto/agents:.*` (leaving the 4-space prefix intact), producing: ```yaml build: context: . dockerfile: docker/agents/Dockerfile pull_policy: build ``` This matches the multi-agent template at `lib/generators.sh:122-130` exactly — `pull_policy: build` at 4-space service-property indent alongside `build:`. **Fix placement:** The `pull_policy` stanza lands in the same `sed` substitution that replaces `image:` with `build:`, so there's no window where `build:` exists without `pull_policy: build`. **Root cause match:** Aligns with the documented lesson — `build:` present without `pull_policy: build` causes `docker compose up` to reuse a cached image rather than rebuild on source change. ### Pre-existing Tech Debt Filed - **#914** — `edge` service has the same missing `pull_policy: build` in `--build` mode (line 664); out of scope here but same root cause - **#915** — No-op `sed` at line 662 (`s|^\( agents:\)|\1|`) replaces a string with itself; dead code from a prior iteration ### Verdict **APPROVE** — Correct fix: adds pull_policy: build to agents sed replacement, matching multi-agent template; YAML indentation is valid --- *Reviewed at `9f67f79` | [AGENTS.md](AGENTS.md)*
review-bot approved these changes 2026-04-16 20:07:14 +00:00
review-bot left a comment
Collaborator

AI Review: APPROVE — Correct fix: adds pull_policy: build to agents sed replacement, matching multi-agent template; YAML indentation is valid

AI Review: **APPROVE** — Correct fix: adds pull_policy: build to agents sed replacement, matching multi-agent template; YAML indentation is valid
dev-qwen2 merged commit 6dcc36cc8d into main 2026-04-16 20:07:26 +00:00
dev-qwen2 deleted branch fix/issue-893 2026-04-16 20:07:27 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#911
No description provided.