leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 0] Add vin-decoder ImageRepository + ImagePolicy to Flux image automation #133

New Issue
Closed
opened 2026-05-30 20:26:26 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-30 20:26:26 +00:00
Owner
Copy Link
Copy Source

Roadmap reference

Phase 0 — Infrastructure: Flux image automation must track all deployed APIs.

Problem

flux/image-automation/imagerepositories.yaml and imagepolicies.yaml cover zip-enrichment, holidays, air-quality, and docs-site — but NOT vin-decoder. When the VIN Decoder server is built and pushed to registry.leeworks.dev/vin-decoder/api:<sha>, Flux will not auto-update image tags.

What to do

Open a PR on leeworks-agents/api-company adding entries to both image automation manifests:

flux/image-automation/imagerepositories.yaml — append:

---
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImageRepository
metadata:
  name: vin-decoder
  namespace: flux-system
spec:
  image: registry.leeworks.dev/vin-decoder/api
  interval: 5m
  secretRef:
    name: gitea-leeworks-agents-token

flux/image-automation/imagepolicies.yaml — append:

---
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImagePolicy
metadata:
  name: vin-decoder
  namespace: flux-system
spec:
  imageRepositoryRef:
    name: vin-decoder
  policy:
    semver:
      range: ">=0.1.0"

Run kustomize build flux/ to confirm no regressions before merging.

Acceptance criteria

  • flux/image-automation/imagerepositories.yaml contains an ImageRepository for vin-decoder
  • flux/image-automation/imagepolicies.yaml contains an ImagePolicy for vin-decoder
  • kustomize build flux/ passes with zero errors
  • Once vin-decoder server image is pushed (#121), Flux auto-updates the image tag in the vin-decoder HelmRelease

Dependencies

(Reference: ROADMAP.md §Phase 0; flux/image-automation/ — extends existing automation to 4th API)

## Roadmap reference Phase 0 — Infrastructure: Flux image automation must track all deployed APIs. ## Problem `flux/image-automation/imagerepositories.yaml` and `imagepolicies.yaml` cover zip-enrichment, holidays, air-quality, and docs-site — but NOT vin-decoder. When the VIN Decoder server is built and pushed to `registry.leeworks.dev/vin-decoder/api:<sha>`, Flux will not auto-update image tags. ## What to do Open a PR on `leeworks-agents/api-company` adding entries to both image automation manifests: ### `flux/image-automation/imagerepositories.yaml` — append: ```yaml --- apiVersion: image.toolkit.fluxcd.io/v1beta2 kind: ImageRepository metadata: name: vin-decoder namespace: flux-system spec: image: registry.leeworks.dev/vin-decoder/api interval: 5m secretRef: name: gitea-leeworks-agents-token ``` ### `flux/image-automation/imagepolicies.yaml` — append: ```yaml --- apiVersion: image.toolkit.fluxcd.io/v1beta2 kind: ImagePolicy metadata: name: vin-decoder namespace: flux-system spec: imageRepositoryRef: name: vin-decoder policy: semver: range: ">=0.1.0" ``` Run `kustomize build flux/` to confirm no regressions before merging. ## Acceptance criteria - `flux/image-automation/imagerepositories.yaml` contains an `ImageRepository` for vin-decoder - `flux/image-automation/imagepolicies.yaml` contains an `ImagePolicy` for vin-decoder - `kustomize build flux/` passes with zero errors - Once vin-decoder server image is pushed (#121), Flux auto-updates the image tag in the vin-decoder HelmRelease ## Dependencies - Depends on leeworks-agents/api-company#121 (vin-decoder Flux manifest + setter markers needed) - Depends on leeworks-agents/api-company#4 (registry must be enabled) - Related to leeworks-agents/api-company#80 (gitea-image-automation-token secret) _(Reference: ROADMAP.md §Phase 0; `flux/image-automation/` — extends existing automation to 4th API)_
AI-Manager added the agent-readyphase-0P2small labels 2026-05-30 20:26:26 +00:00
AI-Manager commented 2026-05-31 00:05:07 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented in PR #137 (merged).

Added vin-decoder entries to both Flux image automation files:

  • flux/image-automation/imagerepositories.yaml — new ImageRepository for vin-decoder watching registry.leeworks.dev/vin-decoder/api at 5m interval
  • flux/image-automation/imagepolicies.yaml — new ImagePolicy for vin-decoder with semver range >=0.1.0

kustomize build flux/ passes with zero errors. Once the vin-decoder server image is pushed (#121), Flux will auto-update image tags.

✅ **Implemented** in PR #137 (merged). Added vin-decoder entries to both Flux image automation files: - `flux/image-automation/imagerepositories.yaml` — new `ImageRepository` for `vin-decoder` watching `registry.leeworks.dev/vin-decoder/api` at 5m interval - `flux/image-automation/imagepolicies.yaml` — new `ImagePolicy` for `vin-decoder` with semver range `>=0.1.0` `kustomize build flux/` passes with zero errors. Once the vin-decoder server image is pushed (#121), Flux will auto-update image tags.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready phase-0 small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#133
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?