Skip to content

[Cognitive Services] Upgrade to 2021-04-30 #15332

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

Merged
merged 4 commits into from Jul 2, 2021
Merged

[Cognitive Services] Upgrade to 2021-04-30 #15332

merged 4 commits into from Jul 2, 2021

Conversation

yangyuan
Copy link
Member

Description

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

@yangyuan
Copy link
Member Author

yangyuan commented Jun 22, 2021

Previously there was a PR but targeted master instead of main.
#15133

Resolved all comments except for SDK caused breaking changes, which include:

  • 1 bug fix. ActionRequired -> ActionsRequired, the name was wrong in previous SDKs, thus can never be used.
  • 1 string-enum to string type change on a un-used field, its always null. SkuTier-> string
  • 1 type name change on a read only field. Only type name change, everything else is same, including field name. IdentityType -> ResourceIdentityType

I tried everything I know of include automapper, but CI still complains type name difference.
I am wondering if we can make an exception for this PR (as impact is very limited), otherwise, I might have to copy the SDK code and modify it to make it compatible with old SDK.

@BethanyZhou
Copy link
Contributor

Hi @yangyuan , main is the new name of master. If you have merged this PR, please check whether your change has been included in main branch.

 "AssemblyFileName","ClassName","Target","Severity","ProblemId","Description","Remediation"
  "Az.CognitiveServices","Microsoft.Azure.Commands.Management.CognitiveServices.GetAzureCognitiveServicesAccountCommand","Get-AzCognitiveServicesAccount","0","3030","The generic type for 'property Type' has been changed from 'System.Nullable`1[Microsoft.Azure.Management.CognitiveServices.Models.IdentityType]' to 'System.Nullable`1[Microsoft.Azure.Management.CognitiveServices.Models.ResourceIdentityType]'. ","Change the generic type for 'property Type' back to 'System.Nullable`1[Microsoft.Azure.Management.CognitiveServices.Models.IdentityType]'."
  "Az.CognitiveServices","Microsoft.Azure.Commands.Management.CognitiveServices.GetAzureCognitiveServicesAccountCommand","Get-AzCognitiveServicesAccount","0","3000","The type of property 'Tier' of type 'Microsoft.Azure.Management.CognitiveServices.Models.Sku' has changed from 'System.Nullable`1[Microsoft.Azure.Management.CognitiveServices.Models.SkuTier]' to 'System.String'.","Change the type of property 'Tier' back to 'System.Nullable`1[Microsoft.Azure.Management.CognitiveServices.Models.SkuTier]'."
  "Az.CognitiveServices","Microsoft.Azure.Commands.Management.CognitiveServices.GetAzureCognitiveServicesAccountCommand","Get-AzCognitiveServicesAccount","0","3010","The property 'ActionRequired' of type 'Microsoft.Azure.Management.CognitiveServices.Models.PrivateLinkServiceConnectionState' has been removed.","Add the property 'ActionRequired' back to type 'Microsoft.Azure.Management.CognitiveServices.Models.PrivateLinkServiceConnectionState'."  

Per my knowledge, the first two are no way to avoid. for the last one can resolved by automapper.

As you claim the impact is very limited, please contact our PM and manager to get approval.

@BethanyZhou BethanyZhou added the Breaking Change Release This PR contains breaking change label Jun 23, 2021
@yangyuan
Copy link
Member Author

Hi @BethanyZhou, I sent an email to you about this PR (not sure if I sent to the right alias, let me know if you didn't receive any email)
I dont know who (PM and manager) should be contacted for this, please help to reroute the email or share contact info.

Thanks

@BethanyZhou
Copy link
Contributor

Hi @BethanyZhou Beisi Zhou FTE, I sent an email to you about this PR (not sure if I sent to the right alias, let me know if you didn't receive any email)
I dont know who (PM and manager) should be contacted for this, please help to reroute the email or share contact info.

Thanks

I didn't receive this email, please contact [email protected]. It's our team email.

@yangyuan
Copy link
Member Author

Hi @BethanyZhou, as talked with email. Damien and Dingmeng agreed the change as long as with clear message to customers will be added the changelog..
And I've modified the change log to includes 3 changes with [breaking changes] prefix.

@BethanyZhou
Copy link
Contributor

Hi please see pipeline azure-powershell - powershell-core (Analyze windows) and suppress the breaking changes that were detected by that pipeline. The way to suppress breaking change: https://github.com/Azure/azure-powershell-pr/wiki/How-to-Release-a-Breaking-Change

@yangyuan
Copy link
Member Author

yangyuan commented Jul 1, 2021

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@yangyuan
Copy link
Member Author

yangyuan commented Jul 1, 2021

@BethanyZhou I ran /azp run and triggered this, all pass.
https://dev.azure.com/azure-sdk/public/_build/results?buildId=980526&view=results

But github still shows Waiting for status to be reported, I guess sth wrong in pipeline.

@BethanyZhou
Copy link
Contributor

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@BethanyZhou BethanyZhou changed the base branch from main to release-2021-07-06 July 2, 2021 02:55
@BethanyZhou BethanyZhou changed the base branch from release-2021-07-06 to main July 2, 2021 02:55
@BethanyZhou
Copy link
Contributor

Hi @yangyuan , approved, will force merge this PR to main branch. The feature will be available in next release.

@dolauli dolauli merged commit 743a3ca into Azure:main Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Release This PR contains breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants