Enable Local File Sources in Provider Discovery #15
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.
When using the installed version of Amplifier (via pip install or uv tool install), users
could only configure providers in ~/.amplifier/settings.yaml with git sources. Local file
paths were not supported in the provider discovery and configuration system, making it
difficult to:
This limitation only affected the global settings configuration - local project configs worked
fine with file sources.
Solution
This PR adds support for local file sources in the provider discovery and configuration
system:
file:///path/to/provider, /absolute/path, ./relative/path)
sources in settings.yaml
AttributeError in certain import contexts