Deploy Phase 5: update image tag to include tsvector search #87

New issue

Closed

opened 2026-03-06 21:10:42 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-06 21:10:42 +00:00

Contributor

Plan

plan-2026-02-26-tf-modularize-postgres -- Phase 5 deployment

Repo

forgejo_admin/pal-e-docs

User Story

As a platform operator
I want the deployed pal-e-docs image updated
So that the tsvector search endpoint and migration go live

Context

PR #84 (tsvector search) and PR #86 (ruff format fix) are merged. CI pipeline #120 built and pushed the image to Harbor. But ArgoCD reads from k8s/deployment.yaml in this repo, which still has the old image tag.

This is a stop-gap — the proper fix is rewiring ArgoCD to use the deployments repo (tracked in todo-argocd-rewire-deployments-repo). For now, update the tag here.

New image tag: c85a39da313a80ebde109895fd281cd7ff7c9275

File Targets

k8s/deployment.yaml — update image tag on line 21 from latest to c85a39da313a80ebde109895fd281cd7ff7c9275

Acceptance Criteria

Image tag updated in k8s/deployment.yaml
ArgoCD detects drift and rolls out new pod
Alembic migration runs (tsvector column + trigger created)
GET /notes/search?q=postgres returns results

Test Expectations

After deploy: curl the search endpoint to verify it returns results
Run: kubectl get pods -n pal-e-docs shows new pod running

Constraints

Only change the image tag. No other modifications.

Checklist

PR opened
No unrelated changes

pal-e-docs project
phase-postgres-5-fulltext-search
todo-argocd-rewire-deployments-repo — the proper long-term fix

### Plan `plan-2026-02-26-tf-modularize-postgres` -- Phase 5 deployment ### Repo `forgejo_admin/pal-e-docs` ### User Story As a platform operator I want the deployed pal-e-docs image updated So that the tsvector search endpoint and migration go live ### Context PR #84 (tsvector search) and PR #86 (ruff format fix) are merged. CI pipeline #120 built and pushed the image to Harbor. But ArgoCD reads from `k8s/deployment.yaml` in this repo, which still has the old image tag. This is a stop-gap — the proper fix is rewiring ArgoCD to use the deployments repo (tracked in `todo-argocd-rewire-deployments-repo`). For now, update the tag here. New image tag: `c85a39da313a80ebde109895fd281cd7ff7c9275` ### File Targets - `k8s/deployment.yaml` — update image tag on line 21 from `latest` to `c85a39da313a80ebde109895fd281cd7ff7c9275` ### Acceptance Criteria - [ ] Image tag updated in `k8s/deployment.yaml` - [ ] ArgoCD detects drift and rolls out new pod - [ ] Alembic migration runs (tsvector column + trigger created) - [ ] `GET /notes/search?q=postgres` returns results ### Test Expectations - [ ] After deploy: `curl` the search endpoint to verify it returns results - Run: `kubectl get pods -n pal-e-docs` shows new pod running ### Constraints - Only change the image tag. No other modifications. ### Checklist - [ ] PR opened - [ ] No unrelated changes ### Related - `pal-e-docs` project - `phase-postgres-5-fulltext-search` - `todo-argocd-rewire-deployments-repo` — the proper long-term fix