Update our Azure rest api specs submodule #4941
Merged
Conversation
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
theunrepentantgeek
requested review from
davefellows,
jakjang,
juan-lee and
matthchr
as code owners
github-project-automation
bot
moved this to In Progress
in Azure Service Operator Roadmap
matthchr
reviewed
Sep 17, 2025
v2/tools/generator/internal/config/configuration_group_shard_test.gox
Outdated
Show resolved
Hide resolved
theunrepentantgeek
force-pushed
the
update/azure-rest-api-specs
branch
from
c920b9e to
8b2135e
Compare
matthchr
approved these changes
Sep 17, 2025
github-project-automation
bot
moved this from In Progress
to Recently Completed
in Azure Service Operator Roadmap
matthchr
moved this from Recently Completed
to Ready for Release
in Azure Service Operator Roadmap
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
Updates our submodule at
v2/specs/azure-rest-api-specsand our generated code.Breaking
Upstream work has resulted in some breaking changes that we'll need to call out in our next release.
CognitiveServices
Compute
In addition, there are many types that are no longer anonymous, but which have official names - our code generator defers to those names when present so some types have been renamed in our code. This will be transparent to CRD users, but anyone consuming our generated code directly may be impacted.
How does this PR make you feel?
Checklist