OpenPublishing.Build fails on every PR: monikerMapping.json packageRoot is missing the docs/ prefix
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- github-actions, json, powershell
- Ambito
- ci-cd, documentation
Direzione di ricerca
Read .openpublishing.publish.config.json and module/mapping/monikerMapping.json, then verify the referenced paths against the contents of module/docs/. Check both preview monikers and confirm the expected path fields with a maintainer who can run the OpenPublishing validation build. Done means the build passes for a PR, including one that does not change documentation.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Every open pull request in this repository currently shows OpenPublishing.Build as failed with the same validation error, including ones that touch no documentation at all:
[Error: PSMD2Yaml_FileLoadFailed] Failed to load file: <...>/module/mapping/monikerMapping.json.
PackageRoot, ReferenceTocUrl, and ConceptualTocUrl are required for every moniker.
PackageRoot should be a valid relative path to docset root.
Confirmed red on #1601, #1572, #1529 and #1611 (and #1611 reproduced it on two different commits, which rules out the branch contents).
Root cause
All three required keys are in fact present in module/mapping/monikerMapping.json, so the first sentence of the error is a red herring. The operative part is the second one: packageRoot is not a valid relative path to the docset root.
.openpublishing.publish.config.json sets "build_source_folder": "module", so the docset root is module/. The mapping declares:
"entra-powershell-preview": {
"packageRoot": "entra-powershell-v1.0",
"conceptualToc": "docs/entra-powershell-v1.0/toc.yml",
...
}
module/entra-powershell-v1.0 does not exist. The contents of module/ are breadcrumb, docfx.json, docs, Entra, EntraBeta and mapping. The reference markdown actually lives in module/docs/entra-powershell-v1.0/ (Applications/, Authentication/, Enable-EntraAzureADAlias.md, ...), which relative to the docset root is docs/entra-powershell-v1.0.
The inconsistency is visible inside the same JSON object: conceptualToc carries the docs/ prefix and packageRoot does not. The same mismatch exists for entra-powershell-beta-preview.
Why it started
module/mapping/monikerMapping.json has not been modified since bfeb177 (2024-03-12, "Update structure"). The module/docs/entra-powershell-v1.0 path has existed since at least 846f29c (2024-09-29). The mapping was written against the earlier layout and was not updated when the docs moved under module/docs/.
Suggested fix
Adding the prefix to both monikers would make the paths resolve:
"entra-powershell-preview": { "packageRoot": "docs/entra-powershell-v1.0", ... }
"entra-powershell-beta-preview": { "packageRoot": "docs/entra-powershell-beta", ... }
I am deliberately filing this as an issue rather than a pull request: OpenPublishing runs inside Microsoft infrastructure, so I cannot execute the docs build to confirm the fix, and getting the docset layout wrong would affect published documentation. Someone who can trigger a validation build is better placed to confirm whether the prefix is the whole story or whether referenceTocUrl and conceptualTocUrl need adjusting alongside it.
Happy to open the PR if a maintainer confirms the direction.
Impact
While this is red, OpenPublishing.Build is not a usable signal on any PR: contributors cannot tell a real documentation regression from the pre-existing failure, and PRs that are otherwise ready carry a red check. #1611 is approved and blocked behind exactly this noise.
- Lingua principale
- PowerShell
- Stelle
- 218
- Fork
- 48
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoftgraph/entra-powershell
-
ToTriage
Difficoltà 2/5 1-3 ore Idoneità per principianti 55/100
microsoftgraph/entra-powershell#1617 ·
-
🪲 unable to connect to entra: InvalidOperation: Unable to find type [Microsoft.Graph.PowerShell.Authentication.ContextScope].Forse già presa @Mike-Crowley l’ha presa 36 giorni fa. ApertaToTriage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
microsoftgraph/entra-powershell#1614 · 4 commenti ·
-
🪲 Characters 0xE2 0x80 0xAF presented in date time signInActivity property when expanded on MacOSApertaToTriage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
microsoftgraph/entra-powershell#1605 ·
-
🪲 Import-Module Microsoft.Entra.Applications / Microsoft.Entra..Beta.Applications throws an error 1.3.0Forse già presa @earbona23 l’ha presa 78 giorni fa. ApertaToTriage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
microsoftgraph/entra-powershell#1603 · 2 commenti · 2 reazioni ·
-
🪲EntraInactiveSignInUser Days LimitationForse già presa @reneemichiko l’ha presa 189 giorni fa. Apertadocumentation
microsoftgraph/entra-powershell#1596 · 1 commento · 1 reazione · 2 assegnatari ·
Tutte le issue di microsoftgraph/entra-powershell
Issue simili
-
needs verification
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 13 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Azure/enterprise-azure-policy-as-code#1463 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
ipfs/ipfs-webui#2507 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
bigbluebutton/bigbluebutton#26638 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100