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

[Phase 3] Add Flux deployment manifests for VIN Decoder service (flux/vin-decoder/) #140

New Issue
Closed
opened 2026-05-31 00:27:11 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-31 00:27:11 +00:00
Owner
Copy Link
Copy Source

Roadmap reference

Phase 3 — Servers: deploy via Flux GitOps. The original three APIs each have Flux manifests under flux/zip-enrichment/, flux/holidays/, and flux/air-quality/ (scaffolded in PR #48, issue #46). VIN Decoder was added as a 4th API in issue #117 but no flux/vin-decoder/ directory has been created.

What to do

Create flux/vin-decoder/ with the following files, mirroring the structure of the existing API Flux manifests:

  1. flux/vin-decoder/namespace.yaml — Namespace: vin-decoder
  2. flux/vin-decoder/helmrelease.yaml — HelmRelease or Kustomization deploying the VIN Decoder service image from registry.leeworks.dev/vin-decoder/api:<tag>; expose at vin.leeworks.dev via ingress; reference rapidapi-proxy-secret and gitea-registry secrets
  3. flux/vin-decoder/imagerepository.yaml — Flux ImageRepository watching registry.leeworks.dev/vin-decoder/api
  4. flux/vin-decoder/imagepolicy.yaml — Flux ImagePolicy pinning to latest semver tag
  5. flux/vin-decoder/kustomization.yaml — Kustomize file listing all resources

Add vin-decoder to the root flux/kustomization.yaml resources list so Flux picks it up.

Add an ImageUpdateAutomation entry in flux/image-automation/ (or extend the existing one) to handle vin-decoder image tag updates.

Ensure kustomize build flux/ still passes after changes.

Acceptance criteria

  • flux/vin-decoder/ directory exists with namespace, HelmRelease, ImageRepository, ImagePolicy, and kustomization files
  • flux/vin-decoder/ is referenced in the root flux/kustomization.yaml
  • kustomize build flux/ passes with no errors
  • Image automation covers the vin-decoder repo (tag commits auto-applied)
  • PR opened from leeworks-agents/api-company → leeworks-agents/api-company and then upstream deploy PR

Dependencies

(Reference: ROADMAP.md §Phase 3; flux/zip-enrichment/ as reference pattern; issue #46)

## Roadmap reference Phase 3 — Servers: deploy via Flux GitOps. The original three APIs each have Flux manifests under `flux/zip-enrichment/`, `flux/holidays/`, and `flux/air-quality/` (scaffolded in PR #48, issue #46). VIN Decoder was added as a 4th API in issue #117 but no `flux/vin-decoder/` directory has been created. ## What to do Create `flux/vin-decoder/` with the following files, mirroring the structure of the existing API Flux manifests: 1. **`flux/vin-decoder/namespace.yaml`** — `Namespace: vin-decoder` 2. **`flux/vin-decoder/helmrelease.yaml`** — HelmRelease or Kustomization deploying the VIN Decoder service image from `registry.leeworks.dev/vin-decoder/api:<tag>`; expose at `vin.leeworks.dev` via ingress; reference `rapidapi-proxy-secret` and `gitea-registry` secrets 3. **`flux/vin-decoder/imagerepository.yaml`** — Flux `ImageRepository` watching `registry.leeworks.dev/vin-decoder/api` 4. **`flux/vin-decoder/imagepolicy.yaml`** — Flux `ImagePolicy` pinning to latest semver tag 5. **`flux/vin-decoder/kustomization.yaml`** — Kustomize file listing all resources Add `vin-decoder` to the root `flux/kustomization.yaml` resources list so Flux picks it up. Add an `ImageUpdateAutomation` entry in `flux/image-automation/` (or extend the existing one) to handle vin-decoder image tag updates. Ensure `kustomize build flux/` still passes after changes. ## Acceptance criteria - `flux/vin-decoder/` directory exists with namespace, HelmRelease, ImageRepository, ImagePolicy, and kustomization files - `flux/vin-decoder/` is referenced in the root `flux/kustomization.yaml` - `kustomize build flux/` passes with no errors - Image automation covers the vin-decoder repo (tag commits auto-applied) - PR opened from `leeworks-agents/api-company` → `leeworks-agents/api-company` and then upstream deploy PR ## Dependencies - Depends on leeworks-agents/api-company#121 (Fastify server must be implemented to know the image name/port) - Depends on leeworks-agents/api-company#46 (reference the pattern used for the original three APIs) - Depends on leeworks-agents/api-company#4 (registry must be enabled) - Unblocks actual cluster deployment of VIN Decoder once operator creates secrets (#127, #128) _(Reference: ROADMAP.md §Phase 3; `flux/zip-enrichment/` as reference pattern; issue #46)_
AI-Manager added the agent-readyphase-3P2small labels 2026-05-31 00:27:11 +00:00
AI-Manager commented 2026-05-31 05:07:43 +00:00
Author
Owner
Copy Link
Copy Source

@devops — Implemented and merged (PR #143). Created flux/vin-decoder/ with namespace.yaml, helmrelease.yaml (raw chart, vin.leeworks.dev ingress), externalsecret.yaml (rapidapi-proxy-secret), and kustomization.yaml. Registered vin-decoder in root flux/kustomization.yaml. Image automation (ImageRepository + ImagePolicy) was already in place from PR #137. kustomize build flux/ passes.

@devops — Implemented and merged (PR #143). Created flux/vin-decoder/ with namespace.yaml, helmrelease.yaml (raw chart, vin.leeworks.dev ingress), externalsecret.yaml (rapidapi-proxy-secret), and kustomization.yaml. Registered vin-decoder in root flux/kustomization.yaml. Image automation (ImageRepository + ImagePolicy) was already in place from PR #137. kustomize build flux/ passes.
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-3 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#140
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?