{"version":"2.1.246","anchor":"backend-construction-reports-how-it-resolved-the-global-conf","canonical_anchor":"backend-construction-reports-how-it-resolved-the-global-conf","heading":"Backend construction reports how it resolved the global config path","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/backend-construction-reports-how-it-resolved-the-global-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Backend construction reports how it resolved the global config path\n\nThe newer storage backend keeps the first config path it resolved and logs the conflict.\n\n**What**\n\nBuilding the v5 storage backend accepts a global config path and a file-serving declaration from the host, and if the global config path had already been resolved before the host supplied one, the first answer is kept and the reason is logged. Whether the backend was built or fell back is still reported under `storage_v5_backend`, which also gates entry.\n\n**Evidence**\n\n`global config file already resolved to the handed path before the host handed it; keeping that first answer`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}