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

[Phase 6] Add vin.leeworks.dev as 4th API subdomain to DNS task (#33) #130

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

Roadmap reference

Phase 6 — Pre-launch: DNS for all API subdomains. VIN Decoder was added as a 4th API (issue #117) after the original DNS task (#33) was created for six subdomains. Issue #106 already added grafana.leeworks.dev as a 7th; this adds vin.leeworks.dev as an 8th.

Problem

Issue #33 lists 6 API/service subdomains (zip, holidays, aqi, docs, status, registry). Issue #106 added grafana as a 7th. The VIN Decoder API — vin.leeworks.dev — is now scoped as the 4th revenue API and needs its own DNS entry, but has no tracking issue.

docs/dns.md must be updated to include vin.leeworks.dev and this issue serves as the tracker to ensure it is not overlooked when the DNS batch is configured.

What to do

When the operator configures DNS for issue #33 (and the grafana addition in #106), also add:

Subdomain Target
vin.leeworks.dev cluster ingress IP
  1. Add the A/CNAME record at the DNS registrar / Cloudflare for vin.leeworks.dev
  2. Verify: dig vin.leeworks.dev +short returns the cluster ingress IP
  3. Update docs/dns.md to include vin.leeworks.dev in the subdomain table

Acceptance criteria

  • dig vin.leeworks.dev +short returns the cluster ingress IP
  • curl -I https://vin.leeworks.dev returns 200 (or 302) from the VIN Decoder service once deployed
  • TLS cert issued for vin.leeworks.dev by cert-manager
  • docs/dns.md updated to list all 8 subdomains (zip, holidays, aqi, docs, status, registry, grafana, vin)
  • Issue #33 should not be closed until all 8 subdomains (including this one) are confirmed

Dependencies

(Reference: ROADMAP.md §Phase 6; docs/dns.md; issue #117 which scoped VIN Decoder as 4th API)

## Roadmap reference Phase 6 — Pre-launch: DNS for all API subdomains. VIN Decoder was added as a 4th API (issue #117) after the original DNS task (#33) was created for six subdomains. Issue #106 already added `grafana.leeworks.dev` as a 7th; this adds `vin.leeworks.dev` as an 8th. ## Problem Issue #33 lists 6 API/service subdomains (`zip`, `holidays`, `aqi`, `docs`, `status`, `registry`). Issue #106 added `grafana` as a 7th. The VIN Decoder API — `vin.leeworks.dev` — is now scoped as the 4th revenue API and needs its own DNS entry, but has no tracking issue. `docs/dns.md` must be updated to include `vin.leeworks.dev` and this issue serves as the tracker to ensure it is not overlooked when the DNS batch is configured. ## What to do When the operator configures DNS for issue #33 (and the grafana addition in #106), also add: | Subdomain | Target | |-----------|--------| | `vin.leeworks.dev` | cluster ingress IP | 1. Add the A/CNAME record at the DNS registrar / Cloudflare for `vin.leeworks.dev` 2. Verify: `dig vin.leeworks.dev +short` returns the cluster ingress IP 3. Update `docs/dns.md` to include `vin.leeworks.dev` in the subdomain table ## Acceptance criteria - `dig vin.leeworks.dev +short` returns the cluster ingress IP - `curl -I https://vin.leeworks.dev` returns 200 (or 302) from the VIN Decoder service once deployed - TLS cert issued for `vin.leeworks.dev` by cert-manager - `docs/dns.md` updated to list all 8 subdomains (zip, holidays, aqi, docs, status, registry, grafana, vin) - Issue #33 should not be closed until all 8 subdomains (including this one) are confirmed ## Dependencies - Depends on leeworks-agents/api-company#33 (main DNS configuration task — do both together) - Depends on leeworks-agents/api-company#122 (vin-decoder repo) and #121 (server) for the service to serve traffic - Related to leeworks-agents/api-company#106 (same pattern — adding grafana as 7th subdomain) _(Reference: ROADMAP.md §Phase 6; docs/dns.md; issue #117 which scoped VIN Decoder as 4th API)_
AI-Manager added the agent-readyphase-6P2smallblocked labels 2026-05-30 15:25:11 +00:00
AI-Manager commented 2026-05-30 20:04:54 +00:00
Author
Owner
Copy Link
Copy Source

@tech-writer — Agent-implemented ✅

Updated docs/dns.md to include vin.leeworks.dev as the 8th subdomain:

  • Added row to Required Records table: vin.leeworks.dev → cluster ingress IP
  • Added dig vin.leeworks.dev +short to the verification script
  • Updated action-required text (7 → 8 A records)
  • Added checklist item [ ] vin.leeworks.dev → DNS record created
  • Updated last-updated date to 2026-05-30

Committed in PR #132 (merged to main).

Remaining operator actions (depends on #33 DNS batch + #121/#122 deployment):

  1. Configure the DNS A record for vin.leeworks.dev → cluster ingress IP (along with issue #33 batch)
  2. Verify: dig vin.leeworks.dev +short
  3. Confirm TLS cert is issued by cert-manager once service is deployed
  4. Close this issue once curl -I https://vin.leeworks.dev returns 200/302
**@tech-writer** — Agent-implemented ✅ Updated `docs/dns.md` to include `vin.leeworks.dev` as the **8th subdomain**: - Added row to Required Records table: `vin.leeworks.dev` → cluster ingress IP - Added `dig vin.leeworks.dev +short` to the verification script - Updated action-required text (7 → 8 A records) - Added checklist item `[ ] vin.leeworks.dev → DNS record created` - Updated last-updated date to 2026-05-30 Committed in PR #132 (merged to main). **Remaining operator actions** (depends on #33 DNS batch + #121/#122 deployment): 1. Configure the DNS A record for `vin.leeworks.dev` → cluster ingress IP (along with issue #33 batch) 2. Verify: `dig vin.leeworks.dev +short` 3. Confirm TLS cert is issued by cert-manager once service is deployed 4. Close this issue once `curl -I https://vin.leeworks.dev` returns 200/302
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 blocked phase-6 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#130
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?