remove isolation key field that had wrong header#42827
Merged
acsoylemezoglu merged 1 commit intoAzure:feature/foundry-releasefrom May 4, 2026
Merged
Conversation
andscho-msft
requested review from
balapv,
dargilco,
glecaros,
johanste and
trrwilson
as code owners
Next Steps to MergeImportant checks have failed. As of today they are not blocking this PR, but in near future they may.Addressing the following failures is highly recommended:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
Comment generated by After APIView workflow run. |
acsoylemezoglu
approved these changes
May 4, 2026
acsoylemezoglu
merged commit 04e0dd0
into
Azure:feature/foundry-release
53 of 73 checks passed
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.
Data Plane API Specification Update Pull Request
Is this review for (select one):
Change Scope
This will cause a breaking change to clients, but I think it's necessary. The client is sending a different header than the backend is looking for. Fixing it to send the right header could break people's apps silently. So it's actually safest to push the break, let people stop sending wrong header, then re-introduce the field sending the correct header so that customers can actually test it functional