Repository navigation
v3.10.0 — the content corrections
Ten threads on microsoft/sql-migration-agent#27 asked about content rather than contracts. That is why the earlier rounds never caught them: the gates were reading schemas and vocabularies, while the errors sat in prerequisite rows, matrix cells and a coverage manifest.
MI Link on AWS EC2 and GCP Compute asked for 5022 + networking. That is one of its two port requirements. The 11000-11999 range carries the distributed availability group's data-replication channel, and it is the half people miss, so a reader could open exactly what the row asked for and still fail.
Log shipping was marked Windows-only. The prerequisite plan's own P03-006 row prepares it on Linux: SQL Server Agent enabled, backup directory exposed over CIFS/Samba. Two documents that ship together disagreed about whether a route exists.
P11-009 demanded the Managed Instance public endpoint whenever SqlPackage ran outside the VNet. VPN, ExpressRoute, peering and private endpoints all reach 1433 without exposing anything, so the row pushed a reader toward the one option a security review will question.
P28-007 keyed its CloudAdmin exception on AVS being the assessment target, while its own rule text keys on the source already running there.
The P20 heading had dropped Fabric. Its summary row kept it, the catalog kept it, its own Fabric-specific row kept it. Two notes still argued a data-carrying BACPAC against Fabric, three releases after the rules, the catalog and the coverage map settled on the DACPAC schema publish.
The coverage manifest pointed at an upstream document path and a test file that exist nowhere the skill is installed, and its cell count was stranded inside a sentence a bad splice had broken.
Two of these were mine, and both had the same shape
The gate comparing the knowledge base with the catalog read summary rows and never section headings, so the P20 heading could lose Fabric under a green check. The downtime vocabulary sweep read the output contract and never the card that renders it, so the card could stay two values short.
Both gates read the second surface now. 28 path comparisons became 56; 34 vocabulary values became 43. Widening the first one immediately found four more heading mismatches, all spelling variants of the same target family.
Advisor knowledge base v3.10, prerequisite knowledge base v1.7. 67 gates green.