Forte/launchpad
6
0
Fork 0
Code Issues 1 Pull Requests 5 Actions Packages Wiki Activity
550 Commits 29 Branches 0 Tags
2a50028e5160753c8d070e40efae258e703b473b
Commit Graph
8 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Stenanddanijel.simeunovic 5913e0c4c0 refactor(apps): move forte-drop postgres from infra to apps 
Per reviewer (danijel): forte-drop's DB deployment belongs in apps/,
not infra/. Straight relocation — same structure (Application +
resources/ subdir), source.path updated to apps/base/forte-drop-postgresql/resources,
wired into apps/overlays/upc-dev. Backup CronJob + RESTORE.md + sealed
pg creds move with it.

Consolidates the whole forte-drop deployment (postgres + web + mcp)
under apps/. The infra PR (#17) is now superseded by this.
 2026-06-04 15:22:05 +02:00
Stenanddanijel.simeunovic 6f6f8c1c55 fix(apps): explicit forte-drop namespace (sync-wave -1, Prune=false) 
Codex review: the apps overlay applies namespaced resources
(keycloak-client Secrets, forte-drop-secrets, PDB) to forte-drop, but
no base created the namespace — first sync on a fresh cluster raced
ahead of the Applications' CreateNamespace and failed with
'namespaces forte-drop not found' until a retry.

Add an explicit Namespace at sync-wave -1 so it exists before the
wave-0 namespaced resources (covers both web + mcp bases via the
shared parent). Prune=false keeps removing a base from cascade-
deleting the namespace + postgres data + the other deployment.
 2026-06-04 15:22:04 +02:00
Stenanddanijel.simeunovic 6d25437e98 feat(apps): add forte-drop-secrets sealed secret 
Sealed forte-drop-secrets with the real UpCloud Managed Object Storage
creds (existing drops bucket), PG creds matching the deployed
forte-drop-pg-creds, and PASSWORD_GATE_SECRET. Consumed by both web +
mcp deployments (envSecretName) and the pg-backup CronJob (S3 creds).
 2026-06-04 15:22:04 +02:00
Stenanddanijel.simeunovic 46f2d2d661 feat(apps): PodDisruptionBudget for forte-drop web (minAvailable 1) 2026-06-04 15:22:04 +02:00
Sten 96db244e03 refactor(apps): move forte-drop postgres from infra to apps
AI Code Review / ai-review (pull_request) Successful in 6s
Details 
Per reviewer (danijel): forte-drop's DB deployment belongs in apps/,
not infra/. Straight relocation — same structure (Application +
resources/ subdir), source.path updated to apps/base/forte-drop-postgresql/resources,
wired into apps/overlays/upc-dev. Backup CronJob + RESTORE.md + sealed
pg creds move with it.

Consolidates the whole forte-drop deployment (postgres + web + mcp)
under apps/. The infra PR (#17) is now superseded by this.
 2026-05-29 10:38:51 +02:00
Sten d6a97a22df fix(apps): explicit forte-drop namespace (sync-wave -1, Prune=false)
AI Code Review / ai-review (pull_request) Successful in 1m40s
Details 
Codex review: the apps overlay applies namespaced resources
(keycloak-client Secrets, forte-drop-secrets, PDB) to forte-drop, but
no base created the namespace — first sync on a fresh cluster raced
ahead of the Applications' CreateNamespace and failed with
'namespaces forte-drop not found' until a retry.

Add an explicit Namespace at sync-wave -1 so it exists before the
wave-0 namespaced resources (covers both web + mcp bases via the
shared parent). Prune=false keeps removing a base from cascade-
deleting the namespace + postgres data + the other deployment.
 2026-05-29 10:25:37 +02:00
Sten c4b7167f9e feat(apps): add forte-drop-secrets sealed secret 
Sealed forte-drop-secrets with the real UpCloud Managed Object Storage
creds (existing drops bucket), PG creds matching the deployed
forte-drop-pg-creds, and PASSWORD_GATE_SECRET. Consumed by both web +
mcp deployments (envSecretName) and the pg-backup CronJob (S3 creds).
 2026-05-29 10:03:57 +02:00
Sten 6bc5bd29b3 feat(apps): PodDisruptionBudget for forte-drop web (minAvailable 1) 2026-05-29 09:31:16 +02:00