Closed ikalligeros closed 3 years ago
I think I get the cause. New cdn service version leaks its implementation to old cdn version. Old version only have type "CacheExpiration", while new version have 6 more types.
Next release would take a few weeks.
You can try new SDK at https://aka.ms/azsdk/java/mgmt. Most code should be compatible (except a few lines on authentication the client), and it should already solved the problem. https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/resourcemanager/azure-resourcemanager-cdn/src/main/java/com/azure/resourcemanager/cdn/models/DeliveryRuleAction.java#L21-L29
Thank you very much @weidongxu-microsoft for the quick follow up! I also tried to find the new types including the ModifyResponseHeader
but i was looking in the wrong place... (azure-mgmt-cdn jars). Thanks for the hint. We will probably move our implementation in the resourcemanager CDN package.
Sure. There is a migration guide in the readme (https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/resourcemanager/docs/MIGRATION_GUIDE.md)
If you having issue during migration, do let us know.
Migration was smooth! I figured out the usage of ClientSecretCredentialBuilder
instead of the previous ApplicationTokenCredentials
. All good!!
Let us know your feedback on the new Java SDK. https://microsoft.qualtrics.com/jfe/form/SV_ehN0lIk2FKEBkwd?Q_CHL=ISSUES
Let us know your feedback on the new Java SDK. https://microsoft.qualtrics.com/jfe/form/SV_ehN0lIk2FKEBkwd?Q_CHL=ISSUES
Done :)
@ikalligeros Thank you very much for providing the feedback. I saw that your response said initially you didn't know which library to use (old vs new), is there anything we can do to make it better to discover?
Describe the bug While trying to get the list of CdnProfiles for a specific azure account, an exception is thrown
Exception or Stack Trace
To Reproduce Unfortunately, this exception occurs on a specific account CDN profile configuration. Not sure how to provide more info without giving away publicly info on this configuration
Code Snippet
Expected behavior Expected behavior that we are seeing on other azure accounts is to actually get the list of CDN profiles without issues
Screenshots No screenshots available
Setup (please complete the following information):
Additional context It seems that this azure account had some old CDN configuration which returns this ModifyResponseHeader in the JSON payload and SDK 1.38.1 doesn't support. When we downgraded to version 1.4.0 this problem was solved.
Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report