Need help to investigate the failure in swagger PR for AKS new API version 2021-09-01

[AbelHu]

Bug Report

• import path of package in question, e.g. .../services/compute/mgmt/2018-06-01/compute
• SDK version e.g. master, latest, 18.1.0
  • Specify the exact commit if possible; one way to get this is the REVISION
    column output by dep status "github.com/Azure/azure-sdk-for-go.
• output of go version

• What happened?
• What did you expect or want to happen?
• How can we reproduce it?
• Anything we should know about your environment.

We created a PR for AKS new API version 2021-09-01 but it hit an error with azure-sdk-for-go in validation test. We need your help as @chengliangli0918 'azure-sdk-for-go-track2' failure needs input from go SDK owner. This check didn't fail in 2021-08-01 and 2021-07-01 API merging PR.

[AbelHu]

ping! This blocks AKS new API version 2021-09-01. We need your help.

[jhendrixMSFT]

Per internal conversation this was introduced in Azure/azure-rest-api-specs#15054 which way likely intentional so that the swagger matches what comes over the wire. The CI failure is non-blocking so you can proceed.

@ArcturusZhang will this continue to show up in future PRs?

[ArcturusZhang]

Per internal conversation this was introduced in Azure/azure-rest-api-specs#15054 which way likely intentional so that the swagger matches what comes over the wire. The CI failure is non-blocking so you can proceed.

@ArcturusZhang will this continue to show up in future PRs?

We have some internal issues with the go version in the agent which runs SDK automation. This is not resolved yet, we hope it could be resolved soon. But for now, we could just ignore that failure, which is not required and will not block you from merging the PR. FYI @AbelHu and it would close this issue now.