Levandor

Test Env Deployment State 2026-08-18

4 min read

Test Env Deployment State 2026-08-18

What is actually running on the test environment as of 2026-08-18, traced end to end from the terraform pin back to the mando commit, and which error-handling MRs that does and does not include. Verified from fetched origin/develop of both repos.

For Agents

Test runs mando image 1.17.0-dev.2749963346.336ce49f, built from mando develop 336ce49f (2026-08-11 09:07 UTC). BE-4067 (MR !601) is NOT on test - it merged ~10 hours after that build and nobody has bumped test since. Everything earlier in the error chain (!585, !592, !597, !599) IS live.

The pin

FactValue
Pin fileterraform/environments/test.tfvars (per-env - see Mando Deployment Ceremony)
mando pin1.17.0-dev.2749963346.336ce49f
Set byIaC commit 16e8241 “feat: bump components version” (Gabor Nagy, 2026-08-11 12:10 UTC / 14:10 CEST)
Same bump also moveddev.tfvars to the identical tag (6 lines each file)
Previous test pin1.17.0-dev.2729271578.24a0f34b (mando 24a0f34b, “Merge branch ‘main’ into develop”, 2026-08-04)

Provenance chain

terraform/environments/test.tfvars
  components.mando.version = "1.17.0-dev.2749963346.336ce49f"
      │
      ├─ pipeline id 2749963346   (mando "Publish Service Docker Dev")
      └─ short sha 336ce49f
             │
             └─ mando develop 336ce49f5dc7a73c5b6dc274819f938f6b653de9
                Andras Lederer, 2026-08-11 09:07 UTC
                "Merge branch 'bugfix/BE-2132-upsert-dedup-key' into 'develop'"   (MR !610)

Apply history (2026-08-11)

Three terraform_apply:test attempts that day; the first two failed.

Time (UTC)IaC pipelineIaC commitResult
12:10-16e8241 pushedpin bump lands
12:37275051412516e8241failed
13:19-cb07b0b “fix: do not ignore application asset tag”-
13:242750720634cb07b0bfailed
13:59-9600b34c “fix: use the correct application asset tag”-
14:1227508453689600b34cApply complete

The two failures were not the mando bump

The timeline lines up exactly with the two “application asset tag” fix commits that sit between the bump and the green apply. 9600b34c is still the origin/develop tip of optimization-universe-iac on 2026-08-18, so nothing has been applied to test since 2026-08-11 14:12 UTC.

Consequence for the error-handling chain

Ancestry checked with git merge-base --is-ancestor <merge> 336ce49f.

MRTicketMerge commitLive on test?
!571BE-35411c4c33a5✅ yes
!585BE-3657 phase 3f84db378✅ yes
!592BE-40003ea0366b✅ yes
!597BE-401437f95d8b✅ yes
!599BE-4047c21e65af✅ yes
!601BE-4067c2c9c9a2❌ NO

MR !601 (refactor: unwall the remaining adapters to mando result, squash 85452c3e, merge c2c9c9a2) merged 2026-08-11 19:26 UTC - roughly 5 hours after the test apply went green and ~10 hours after the image it deployed was built.

Two further merges from the same day are also absent for the same reason (they postdate the 09:07 UTC build):

  • 4d6cf7a1 BE-4282, merged 14:24 UTC
  • 92213459 BE-4017, merged 15:11 UTC

Do not read test telemetry as BE-4067 behaviour

Any Datadog assessment of error.errors / error.details / the tree-shaped error.stack on test is measuring the pre-!601 world. The BE-4067 error DX clarity telemetry delta is not observable there yet.

Images that contain !601 but are unpinned

Both published and green in mando CI, neither referenced by any *.tfvars:

Image tagmando commitWhat it adds
1.17.0-dev.2751762903.c2c9c9a2c2c9c9a2the exact !601 merge
1.17.0-dev.2756529188.b5770766b5770766 (develop tip, 2026-08-13)!601 plus BE-4312 (afrr activation forecast timespan) and the forecast-mode fix

The second tag was read verbatim from the “Publish Service Docker Dev” job log of mando pipeline 2756529188. b5770766 is still mando’s origin/develop tip on 2026-08-18, so pinning that tag would put test on develop tip.

How to re-derive this

IAC=/Volumes/bandi/coding/poc/optimization-universe-iac
M=/Volumes/bandi/coding/poc/mando
 
git -C $IAC fetch origin develop && git -C $M fetch origin develop
 
# the pin (NEVER read the working tree - that clone is on rc/1.11.0 from May)
git -C $IAC show origin/develop:terraform/environments/test.tfvars | grep -A2 '  mando = {'
 
# what the short sha is
git -C $M log -1 --format='%H%n%an%n%ad%n%s' --date=iso 336ce49f
 
# is MR X live on test?
git -C $M merge-base --is-ancestor <merge-sha> 336ce49f && echo LIVE || echo NOT-LIVE
 
# what is on develop but not deployed
git -C $M log --merges --format='%h %ad %s' --date=short 336ce49f..origin/develop

Graph View

Backlinks