fix(runtime): resolve provider preflight from the configured source - #358
Merged
Merged
Conversation
Add lazy credential preflight and configured-source metadata validation without installed entry-point fallback. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Resolve credential preflight against combined effective source overrides while preserving legacy no-source behavior and fail-closed origins. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Match the actual ContextValidator asynchronous context API in generated test fixtures. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Resolve provider banner metadata from static maps and humanized identifiers without importing configured provider modules. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
This was referenced Sep 21, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Credential preflight and the provider banner can import an ambient provider before the session resolves its configured source. That conflicts with Core's canonical source-module identity checks and can validate credentials against the wrong provider metadata.
Resolve metadata through the prepared bundle resolver only when an unset credential placeholder requires it. Honor entry, module, and override sources; reject metadata from another root; and render the banner without importing provider implementations. The four original PR110 companion commits are preserved as cherry-picks onto current main
dbf633f.Validation on Python 3.13, in separate virtual environments:
35f7aae(dev wheel): the same full-suite result; 34 focused credential/source and provider-cleanup tests also passed separately.The initial local run had three ANSI-color assertions fail under inherited
NO_COLOR=1andTERM=dumb; the scope tests and both full suites passed withNO_COLORunset andTERM=xterm-256color. No test was modified or newly excluded.Land this backwards-compatible prerequisite before microsoft/amplifier-core#109/#110. This source change does not publish packages or modify installed environments.