fix: clarify AI provider collision warnings - #28549
Merged
Merged
Conversation
Contributor
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
ssncferreira
marked this pull request as ready for review
August 25, 2026 17:00
pawbana
approved these changes
Aug 25, 2026
ssncferreira
marked this pull request as draft
August 26, 2026 08:13
ssncferreira
force-pushed
the
fix/ai-provider-warning-contract
branch
3 times, most recently
from
August 26, 2026 08:50
2b2bd78 to
3dcd067
Compare
ssncferreira
force-pushed
the
fix/ai-provider-warning-contract
branch
from
August 26, 2026 08:53
3dcd067 to
f4d6968
Compare
ssncferreira
marked this pull request as ready for review
August 26, 2026 09:03
pawbana
approved these changes
Aug 26, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
AI provider collision warnings were only partially asserted, and the update coverage did not exercise a provider changing from a distinct hostname to a colliding hostname.
Assert the complete warning consistently across create, get, list, and update responses, cover collisions introduced by base URL and enabled-state updates, and only return the proxy-specific warning when AI Gateway Proxy is enabled. Clarify that lifecycle status values are reported by the provider metrics.
Follow-up to #28208.
Note
Generated by Coder Agents for @ssncferreira.