-
Notifications
You must be signed in to change notification settings - Fork 5.8k
API Cleanup initial pass(merge sqush jugonzales/agents-optimization-v2preview) #43927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
glecaros
merged 5 commits into
Azure:feature/foundry-release
from
YoYoJa:jessli/Optimize-clean2
Jun 12, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0c7b766
rebase to /feature/foundry-release and merge sqush jugonzales/agents-…
YoYoJa 652cae6
resolve missing file
YoYoJa ac5641e
address comment for minValue of max_candidates
YoYoJa 15c9a73
address comments of OptimizationInlineDatasetInput.type
YoYoJa 3179780
address coment of OptimizationJobListItem
YoYoJa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
2,001 changes: 589 additions & 1,412 deletions
2,001
specification/ai-foundry/data-plane/Foundry/openapi3/v1/microsoft-foundry-openapi3.json
Large diffs are not rendered by default.
Oops, something went wrong.
1,002 changes: 212 additions & 790 deletions
1,002
specification/ai-foundry/data-plane/Foundry/openapi3/v1/microsoft-foundry-openapi3.yaml
Large diffs are not rendered by default.
Oops, something went wrong.
2,001 changes: 589 additions & 1,412 deletions
2,001
...oundry/data-plane/Foundry/openapi3/virtual-public-preview/microsoft-foundry-openapi3.json
Large diffs are not rendered by default.
Oops, something went wrong.
1,002 changes: 212 additions & 790 deletions
1,002
...oundry/data-plane/Foundry/openapi3/virtual-public-preview/microsoft-foundry-openapi3.yaml
Large diffs are not rendered by default.
Oops, something went wrong.
319 changes: 120 additions & 199 deletions
319
specification/ai-foundry/data-plane/Foundry/src/agents-optimization/models.tsp
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
asked in the other PR, is there a strong reason not to use the opt-in key we were using before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As V2 removed lots of useless properties from V1 to align with the job guidelines more correctly, but V1 is already released in previous sdk version per Justin, so bumped to V2 here to make it less confusion.
And service side is still supporting V1 as a backward now for smooth inergration from UI and kinds of tests platform while rollout the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the whole point of the endpoints being in preview, is to signal users that breaking changes are to be expected, not sure the value we are adding by replacing the string for the opt-in key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still need do backward from service side, since UI and kinds of our tests also need time to rollout to different region to switch from V1 to V2.