Skip to content

Fix Mongo inventory manifest load order - #1369

Merged
azurras merged 1 commit into
mainfrom
codex/fix-mongo-inventory-manifest-load
Aug 13, 2026
Merged

Fix Mongo inventory manifest load order#1369
azurras merged 1 commit into
mainfrom
codex/fix-mongo-inventory-manifest-load

Conversation

@azurras

@azurras azurras commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Summary

  • load the immutable domain collection manifest in the same mongosh evaluation unit as the dependent inventory program
  • preserve the fixed loopback database and strict inventory-result validation
  • add a regression for load-before-use ordering

Root cause

Mongosh processes --eval before --file, so the prior command evaluated the inventory body before DomainCollectionManifest existed.

Validation

  • RED: focused contract failed 1/1 against the old seven-argument invocation
  • GREEN: focused contract passed 1/1
  • PowerShell 7 Operations suite: 91/91
  • Windows PowerShell 5.1 + Pester 5.9 Operations suite: 91/91
  • both changed files parse on both hosts
  • live read-only inventory: complete=true; 14 collections; 52 kinds; 126 indexes; all manifest compliance checks true
  • independent review: APPROVED, no Critical/Important findings

@azurras
azurras merged commit e073823 into main Aug 13, 2026
8 checks passed
@azurras
azurras deleted the codex/fix-mongo-inventory-manifest-load branch August 14, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant