certctl

mirror of https://github.com/shankar0123/certctl.git synced 2026-06-07 16:41:36 +00:00

Files

T

shankar0123 c8624a7fae fix(deploy/test): libest IP collision with tls-init (10.30.50.9 → 10.30.50.10)

Two services on the certctl-test bridge network were pinned to the
same static IP: certctl-tls-init (line 91) and libest-client
(line 472). The pre-Phase-5 per-vendor matrix structurally hid this:
- tls-init is profile-less ⇒ always runs
- libest-client is profiles=[est-e2e] ⇒ only runs when est-e2e
  job brings it up
- est-e2e and deploy-e2e historically lived in DIFFERENT CI jobs ⇒
  separate docker networks ⇒ no collision

The collision would surface the moment any single CI job invokes
both `--profile deploy-e2e` and `--profile est-e2e`, or the moment a
local operator runs `docker compose --profile=*` for full-stack
debugging. Pre-emptive fix.

Move libest to 10.30.50.10 (next free address; allocated range was
10.30.50.2-9 + 20-30, the entire 10-19 sub-range was unused).

NOT the cause of the deploy-vendor-e2e "certctl-test-server is
unhealthy" failure in CI run 25194251740 — libest isn't in
profile=deploy-e2e and never started in that run. Real cause for
that failure is being investigated in a separate commit (CI
diagnostic dumping).

2026-04-30 23:36:54 +00:00

helm

Update LICENSE metadata

2026-04-26 23:29:59 +00:00

test

fix(deploy/test/libest): drop make-time CFLAGS/LDFLAGS pass-through

2026-04-30 23:21:59 +00:00

.env.example

fix: externalize credentials and add agent key volume persistence

2026-03-20 01:20:27 -04:00

docker-compose.demo.yml

fix(deploy,db,handler): close fresh-clone postgres init failure + 4 ride-along audit findings (U-3 master)