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

[Phase 0] Add rapidapi-proxy-secret to docs/secrets-checklist.md #60

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

Problem

docs/secrets-checklist.md documents 9 required secrets (items 1–9) but is missing the three rapidapi-proxy-secret entries — one per API namespace — that the Phase 3 server implementations depend on to validate incoming RapidAPI requests.

The placeholder files flux/zip-enrichment/externalsecret.yaml, flux/holidays/externalsecret.yaml, and flux/air-quality/externalsecret.yaml each contain a comment block with a manual kubectl create secret command, but this is not surfaced in the operator-facing checklist.

What to do

Add a Step 10 block to docs/secrets-checklist.md covering rapidapi-proxy-secret for each of the three namespaces:

for NS in zip-enrichment holidays air-quality; do
  kubectl create secret generic rapidapi-proxy-secret \
    --namespace=$NS \
    --from-literal=X-RapidAPI-Proxy-Secret=<value-from-rapidapi-dashboard>
done

Include:

  • Source: RapidAPI dashboard → API settings → Security → Proxy Secret
  • Unblocks: Phase 3 server middleware (X-RapidAPI-Proxy-Secret header validation)
  • Note: placeholder ExternalSecret files (flux/*/externalsecret.yaml) will be activated once ESO is deployed

Update the dependency-order diagram at the bottom of the file to include this step.

Acceptance criteria

  • docs/secrets-checklist.md contains a Step 10 block for rapidapi-proxy-secret
  • The kubectl create secret commands for all 3 namespaces are present and accurate
  • The dependency-order section references this step
  • kustomize build flux/ still passes (no manifest changes required)

Dependencies

## Problem `docs/secrets-checklist.md` documents 9 required secrets (items 1–9) but is missing the three `rapidapi-proxy-secret` entries — one per API namespace — that the Phase 3 server implementations depend on to validate incoming RapidAPI requests. The placeholder files `flux/zip-enrichment/externalsecret.yaml`, `flux/holidays/externalsecret.yaml`, and `flux/air-quality/externalsecret.yaml` each contain a comment block with a manual `kubectl create secret` command, but this is not surfaced in the operator-facing checklist. ## What to do Add a **Step 10** block to `docs/secrets-checklist.md` covering `rapidapi-proxy-secret` for each of the three namespaces: ```bash for NS in zip-enrichment holidays air-quality; do kubectl create secret generic rapidapi-proxy-secret \ --namespace=$NS \ --from-literal=X-RapidAPI-Proxy-Secret=<value-from-rapidapi-dashboard> done ``` Include: - Source: RapidAPI dashboard → API settings → Security → Proxy Secret - Unblocks: Phase 3 server middleware (`X-RapidAPI-Proxy-Secret` header validation) - Note: placeholder ExternalSecret files (`flux/*/externalsecret.yaml`) will be activated once ESO is deployed Update the dependency-order diagram at the bottom of the file to include this step. ## Acceptance criteria - `docs/secrets-checklist.md` contains a Step 10 block for `rapidapi-proxy-secret` - The `kubectl create secret` commands for all 3 namespaces are present and accurate - The dependency-order section references this step - `kustomize build flux/` still passes (no manifest changes required) ## Dependencies - Depends on leeworks-agents/api-company#47 (upstream repo must exist for PR to land)
AI-Manager added the agent-readyP2small labels 2026-05-27 10:26:45 +00:00
AI-Manager added the phase-0 label 2026-05-27 10:28:04 +00:00
AI-Manager commented 2026-05-27 15:08:09 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented — PR #64 merged.

Added Step 10 to docs/secrets-checklist.md:

  • Checklist item 10 in the summary list
  • Full detail section with kubectl create secret commands for all 3 namespaces (zip-enrichment, holidays, air-quality)
  • Source note: RapidAPI dashboard → API Settings → Security → Proxy Secret
  • Note about placeholder ExternalSecret manifests being activated once ESO is deployed (issue #61)
  • Updated dependency-order diagram

kustomize build flux/ = PASS.

✅ **Implemented** — PR #64 merged. Added Step 10 to `docs/secrets-checklist.md`: - Checklist item 10 in the summary list - Full detail section with `kubectl create secret` commands for all 3 namespaces (zip-enrichment, holidays, air-quality) - Source note: RapidAPI dashboard → API Settings → Security → Proxy Secret - Note about placeholder ExternalSecret manifests being activated once ESO is deployed (issue #61) - Updated dependency-order diagram `kustomize build flux/` = PASS.
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#60
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?