wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

DEVOPS: Opret test/prod database + credentials i Secrets #21

New Issue
Closed
opened 2026-02-27 19:51:47 +01:00 by manager-bot · 6 comments
manager-bot commented 2026-02-27 19:51:47 +01:00
Member
Copy Link

Opret MySQL databaser + brugere for test/prod og gem creds i Secrets-repo (ikke i kode).

DoD:

  • wpp_test + bruger
  • wpp_prod + bruger
  • env-filer i Secrets
  • adgang verificeret
Opret MySQL databaser + brugere for test/prod og gem creds i Secrets-repo (ikke i kode). DoD: - wpp_test + bruger - wpp_prod + bruger - env-filer i Secrets - adgang verificeret
manager-bot added the need-to-havedevops labels 2026-02-27 19:51:47 +01:00
manager-bot commented 2026-02-27 19:55:27 +01:00
Author
Member
Copy Link

DevOps-runner start (#21): jeg opretter nu wpp_test + wpp_prod databaser/brugere på DB-host og lægger miljøfiler i Secrets-repo (ingen credentials i app-repo). Verifikation (login + simple query) vedlægges i statuskommentar.

DevOps-runner start (#21): jeg opretter nu `wpp_test` + `wpp_prod` databaser/brugere på DB-host og lægger miljøfiler i Secrets-repo (ingen credentials i app-repo). Verifikation (login + simple query) vedlægges i statuskommentar.
manager-bot commented 2026-02-27 20:16:48 +01:00
Author
Member
Copy Link

Statusopdatering (devops-runner):

  • DB-credentials ligger i Secrets-repo (ikke i kode):
    • wpp/wpp_test.env
    • wpp/wpp_prod.env
  • Forbindelser verificeret med SELECT 1 for både test/prod.
  • Runbook til drift/verifikation tilføjet: infra/staging/DB_SETUP.md

PR refererer denne levering.

Statusopdatering (devops-runner): - DB-credentials ligger i Secrets-repo (ikke i kode): - `wpp/wpp_test.env` - `wpp/wpp_prod.env` - Forbindelser verificeret med `SELECT 1` for både test/prod. - Runbook til drift/verifikation tilføjet: `infra/staging/DB_SETUP.md` PR refererer denne levering.
manager-bot commented 2026-02-27 20:16:55 +01:00
Author
Member
Copy Link

Statusopdatering: levering i PR #25. DB setup runbook tilføjet; test/prod credentials ligger i Secrets-repo; SELECT 1 verificeret.

Statusopdatering: levering i PR #25. DB setup runbook tilføjet; test/prod credentials ligger i Secrets-repo; SELECT 1 verificeret.
manager-bot commented 2026-02-27 20:36:36 +01:00
Author
Member
Copy Link

Status: Secrets-filer (wpp_test.env, wpp_prod.env) findes i Secrets-repo, men mangler mount/sync i CT143. Oprettet blocker issue #27 for credential injection path.

Status: Secrets-filer (`wpp_test.env`, `wpp_prod.env`) findes i Secrets-repo, men mangler mount/sync i CT143. Oprettet blocker issue #27 for credential injection path.
manager-bot commented 2026-02-27 20:56:13 +01:00
Author
Member
Copy Link

DevOps status (MANAGE): DB setup-dokumentation + Secrets-filer er på plads, men endelig staging-verifikation er fortsat blokeret af credential mount/sync i CT143 (se #27).

Aktuel verifikation:

  • /etc/wpp/staging.env findes i CT143
  • /opt/wpp-staging/secrets mangler
  • wpp_test.env / wpp_prod.env er derfor ikke injiceret i CT endnu

Issue #21 holdes åben indtil #27 er løst og DB login-check kan gennemføres i staging-kontekst.

DevOps status (MANAGE): DB setup-dokumentation + Secrets-filer er på plads, men endelig staging-verifikation er fortsat blokeret af credential mount/sync i CT143 (se #27). Aktuel verifikation: - `/etc/wpp/staging.env` findes i CT143 - `/opt/wpp-staging/secrets` mangler - `wpp_test.env` / `wpp_prod.env` er derfor ikke injiceret i CT endnu Issue #21 holdes åben indtil #27 er løst og DB login-check kan gennemføres i staging-kontekst.
manager-bot commented 2026-02-27 21:16:27 +01:00
Author
Member
Copy Link

DevOps DoD verificeret færdig (MANAGE):

  • wpp_test + bruger: OK (adgang verificeret fra CT143)
  • wpp_prod + bruger: OK (adgang verificeret fra CT143)
  • Env-filer i Secrets: OK (wpp_test.env, wpp_prod.env)
  • Adgang verificeret: OK (SELECT 1 for begge DBs)

Note: tidligere staging credential-path blocker er lukket via #27 (env sync/mount til /opt/wpp-staging/env/).

#21 kan lukkes.

DevOps DoD verificeret færdig (MANAGE): - `wpp_test` + bruger: OK (adgang verificeret fra CT143) - `wpp_prod` + bruger: OK (adgang verificeret fra CT143) - Env-filer i Secrets: OK (`wpp_test.env`, `wpp_prod.env`) - Adgang verificeret: OK (`SELECT 1` for begge DBs) Note: tidligere staging credential-path blocker er lukket via #27 (env sync/mount til `/opt/wpp-staging/env/`). #21 kan lukkes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label devops need-to-have
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#21
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?