-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
cdn release #23887
cdn release #23887
Conversation
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.
Don't quite understand the breaking, can we use the same commit of the Swagger for the exsiting SDK instead of the latest one to avoid breaking change?
Because the old commit id does not work so we take the latest one |
My understanding is by default we should use the old commit id to avoid breaking change, is it possbile to investigate why the old one does not work instead of using the latest one directly, especially the latest one contains breaking change. |
resourceGroupName, | ||
profileName, | ||
endpointName, | ||
customDomainName, |
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 need to revert these changes
} | ||
|
||
// #endregion | ||
|
||
// Operation Specifications |
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.
+1
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.
LGTM
release issue:https://github.com/Azure/sdk-release-request/issues/3545