fix: Handle non-default base path for OpenAI compatible model fetching #3566
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 workingon the PR for docs configuring Docker model runner which uses OpenAI compatible API backend, I had some issues when goose configure would error when it wouldn't figure out how to fetch the models.
This PR fixes an issue when a non-default OPENAI_BASE_PATH is configured. I think it might still fail in some corner cases where API is not on the /v1/chat/completions path, but it's better than hardcoding the v1/models.