Rename pal-e-app repo to pal-e-docs-app

forgejo_admin commented

2026-03-28 05:32:46 +00:00

Owner

Type

Feature

Lineage

Board: board-pal-e-docs
Story: story:superuser-maintain
Arch: arch:naming, arch:k8s-deploy, arch:keycloak

Repo

Cross-repo: pal-e-app, pal-e-services, pal-e-deployments, claude-custom

User Story

As the superuser, I need pal-e-app renamed to pal-e-docs-app so the naming convention is clear: this is the pal-e-docs frontend, not a generic app template. Convention: {project}-app = frontend for {project}.

Context

Current state:

Forgejo repo: pal-e-app
k8s namespace: pal-e-app
Keycloak client ID: pal-e-app (master realm)
Harbor project: pal-e-app
ArgoCD app: pal-e-app
Tailscale funnel: pal-e-app.tail5b443a.ts.net
Overlay: pal-e-deployments/overlays/pal-e-app/

All need renaming to pal-e-docs-app.

Scope — 8 atomic tasks, 3 parallel waves

Wave A (independent, parallel):

Rename Forgejo repo via admin UI/API
Create new Keycloak client pal-e-docs-app in master realm (copy settings from pal-e-app)
Create new Harbor project pal-e-docs-app (terraform var.services)
Rename overlay directory overlays/pal-e-app/ → overlays/pal-e-docs-app/ in pal-e-deployments

Wave B (depends on Wave A):
5. Update pal-e-services terraform: var.services key pal-e-app → pal-e-docs-app, new namespace, ArgoCD app, funnel hostname
6. Update AUTH_KEYCLOAK_ID=pal-e-docs-app in pal-e-deployments overlay deployment-patch.yaml
7. Update package.json name, any internal repo name references in pal-e-docs-app

Wave C (apply):
8. Run tofu apply for pal-e-services, verify ArgoCD syncs with new name

File Targets

pal-e-services/terraform/k3s.tfvars (services map key)
pal-e-deployments/overlays/pal-e-docs-app/ (renamed directory)
pal-e-docs-app/package.json (name field)
claude-custom: CLAUDE.md repo references

Constraints

Old namespace must be cleaned up after migration (delete pal-e-app namespace)
Old Keycloak client should remain temporarily (active sessions)
Woodpecker CI must be re-activated on new repo name
Local checkout ~/pal-e-app can keep its directory name (just update remote URL)

Acceptance Criteria

kubectl get ns pal-e-docs-app exists
ArgoCD app pal-e-docs-app is Healthy + Synced
https://pal-e-docs-app.tail5b443a.ts.net serves the app
Keycloak auth works with new client ID
CI pipeline runs on new repo name
Old pal-e-app namespace deleted

Checklist

Rename repo on Forgejo
Create Keycloak client
Update Harbor project
Rename overlay directory
Update pal-e-services terraform
Update deployment-patch env vars
Update package.json
Apply terraform
Verify ArgoCD sync
Delete old namespace
Update CLAUDE.md references

Test Expectations

App loads at new URL with Keycloak auth
CI pipeline builds and deploys on push to main

Previous scope questions: namespace change (YES), Keycloak (YES, client ID is pal-e-app), funnel (YES)
Blocks: pal-e-app wget auth PR #89 (hold until rename completes)
Pattern: same rename done for pal-e-docs → pal-e-api (PRs #217-#219)

### Type Feature ### Lineage - Board: board-pal-e-docs - Story: story:superuser-maintain - Arch: arch:naming, arch:k8s-deploy, arch:keycloak ### Repo Cross-repo: pal-e-app, pal-e-services, pal-e-deployments, claude-custom ### User Story As the superuser, I need pal-e-app renamed to pal-e-docs-app so the naming convention is clear: this is the pal-e-docs frontend, not a generic app template. Convention: {project}-app = frontend for {project}. ### Context Current state: - Forgejo repo: `pal-e-app` - k8s namespace: `pal-e-app` - Keycloak client ID: `pal-e-app` (master realm) - Harbor project: `pal-e-app` - ArgoCD app: `pal-e-app` - Tailscale funnel: `pal-e-app.tail5b443a.ts.net` - Overlay: `pal-e-deployments/overlays/pal-e-app/` All need renaming to `pal-e-docs-app`. ### Scope — 8 atomic tasks, 3 parallel waves **Wave A (independent, parallel):** 1. Rename Forgejo repo via admin UI/API 2. Create new Keycloak client `pal-e-docs-app` in master realm (copy settings from pal-e-app) 3. Create new Harbor project `pal-e-docs-app` (terraform var.services) 4. Rename overlay directory `overlays/pal-e-app/` → `overlays/pal-e-docs-app/` in pal-e-deployments **Wave B (depends on Wave A):** 5. Update pal-e-services terraform: var.services key `pal-e-app` → `pal-e-docs-app`, new namespace, ArgoCD app, funnel hostname 6. Update `AUTH_KEYCLOAK_ID=pal-e-docs-app` in pal-e-deployments overlay deployment-patch.yaml 7. Update package.json name, any internal repo name references in pal-e-docs-app **Wave C (apply):** 8. Run `tofu apply` for pal-e-services, verify ArgoCD syncs with new name ### File Targets - pal-e-services/terraform/k3s.tfvars (services map key) - pal-e-deployments/overlays/pal-e-docs-app/ (renamed directory) - pal-e-docs-app/package.json (name field) - claude-custom: CLAUDE.md repo references ### Constraints - Old namespace must be cleaned up after migration (delete pal-e-app namespace) - Old Keycloak client should remain temporarily (active sessions) - Woodpecker CI must be re-activated on new repo name - Local checkout ~/pal-e-app can keep its directory name (just update remote URL) ### Acceptance Criteria - [ ] `kubectl get ns pal-e-docs-app` exists - [ ] ArgoCD app `pal-e-docs-app` is Healthy + Synced - [ ] `https://pal-e-docs-app.tail5b443a.ts.net` serves the app - [ ] Keycloak auth works with new client ID - [ ] CI pipeline runs on new repo name - [ ] Old `pal-e-app` namespace deleted ### Checklist - [ ] Rename repo on Forgejo - [ ] Create Keycloak client - [ ] Update Harbor project - [ ] Rename overlay directory - [ ] Update pal-e-services terraform - [ ] Update deployment-patch env vars - [ ] Update package.json - [ ] Apply terraform - [ ] Verify ArgoCD sync - [ ] Delete old namespace - [ ] Update CLAUDE.md references ### Test Expectations - App loads at new URL with Keycloak auth - CI pipeline builds and deploys on push to main ### Related - Previous scope questions: namespace change (YES), Keycloak (YES, client ID is pal-e-app), funnel (YES) - Blocks: pal-e-app wget auth PR #89 (hold until rename completes) - Pattern: same rename done for pal-e-docs → pal-e-api (PRs #217-#219)

forgejo_admin commented

2026-03-28 05:39:54 +00:00

Author

Owner

Scope Review: NEEDS_REFINEMENT

Review note: review-510-2026-03-27
Cross-repo rename with 10+ file targets across 4+ repos -- too large for a single agent pass.

Issues found:

"ArgoCD app reference in pal-e-services" file target is wrong -- no pal-e-app references exist in pal-e-services
8 undocumented file targets: pal-e-platform monitoring TF, CI scripts (2), package.json, e2e specs, keycloak.ts, playwright.config.ts, k8s namespace
4 missing acceptance criteria: monitoring TF, CI scripts, Keycloak client, namespace decision
3 scope questions need human decision: k8s namespace change, Keycloak OIDC client, Tailscale funnel hostname

Recommend decomposition via template-board into 5-7 tickets (one per repo + admin actions).

## Scope Review: NEEDS_REFINEMENT Review note: `review-510-2026-03-27` Cross-repo rename with 10+ file targets across 4+ repos -- too large for a single agent pass. **Issues found:** - "ArgoCD app reference in pal-e-services" file target is wrong -- no pal-e-app references exist in pal-e-services - 8 undocumented file targets: pal-e-platform monitoring TF, CI scripts (2), package.json, e2e specs, keycloak.ts, playwright.config.ts, k8s namespace - 4 missing acceptance criteria: monitoring TF, CI scripts, Keycloak client, namespace decision - 3 scope questions need human decision: k8s namespace change, Keycloak OIDC client, Tailscale funnel hostname Recommend decomposition via template-board into 5-7 tickets (one per repo + admin actions).