Repository navigation
Conversation
added 2 commits
October 9, 2026 13:48
…for both getRPExtendedInfo and getRPExtendedInfoOperationResult
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
Contributor readiness: required accessWarning The access issues below can prevent PR approvals from counting or block Azure DevOps pipeline runs.
Internal contributors: setup / renew required access. Recheck: Contributors with verified access (1)Public Azure membership and repository write access verified.
Non-blocking report; external fork contributions are allowed. GitHub review rules still apply. |
github-actions
Bot
added
ARMReview
resource-manager
TypeSpec
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
Comment generated by After APIView workflow run. |
github-actions
Bot
added
ARMAutoSignedOff-IncrementalTSP
ARMAutoSignedOff-Test
and removed
ARMAutoSignedOff-Test
ARMAutoSignedOff-Trivial
labels
iwrinshow
added
the
PublishToCustomers
This was referenced Oct 10, 2026
github-actions
Bot
added
BreakingChangeReviewRequired
github-actions
Bot
added
NotReadyForARMReview
ARMAutoSignedOff-Test
and removed
ARMSignedOff
github-actions
Bot
removed
ARMAutoSignedOff-Test
ARMAutoSignedOff-IncrementalTSP
labels
…LRO initiator The operation result endpoint declared ArmLroLocationHeader on its 202 response. That decorator carries @pollingLocation/@finalLocation, which tells the SDK emitters that the operation *starts* a long running operation. The result is that the Java emitter generates a poller for the very endpoint that is the poll target, and because a GET has no final result metadata of its own the poller is typed PollResult<Void>. RPExtendedInfoResourceListInner is generated but never referenced, so the feature returns nothing in Java. The Location header is still declared and still returned, so the REST contract is unchanged. The only generated swagger difference is the header description. Polling semantics continue to come from the getRPExtendedInfo POST, which carries final-state-via: location and final-state-schema. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c58056c6-6882-48a3-bc36-04b13e2305cc
…tendedinfo-result-lro Model getRPExtendedInfoOperationResult as a plain GET rather than an LRO initiator
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.
Click here to open a PR for only SDK configuration.