There are two problem:

• The azure-rest-api-specs ci framework inputJson only contain the relatedReadmeMdFiles (regaring it as swagger project), no relatedTypeSpecProjectFolder
• .NET automation failed to create the scaffolding for this new RP when it is from swagger.

Root cause:
The mgmt-plane sdk template/scaffolding now only suitable for typespec project. This is a swagger project (identified by the azure-rest-api-specs ci framework, maybe wrong), and it is a new service, so it tried to use mgmt-plane sdk template to generate the scaffolding which is not correct, the generated configure file is not correct.

@chunyu3 , the policy requires all the new service use TypeSpec. Is this service an exception to use Swagger?

@chunyu3 , the policy requires all the new service use TypeSpec. Is this service an exception to use Swagger?

@raych1 it uses TypeSpec. But the ci framework somehow identified it as swagger project by mistake.

@chunyu3 is this a bug in the .NET automation scripts?

@chunyu3 is this a bug in the .NET automation scripts?

Current new service of management-plane only can be generated from Typespec, so the mgmt-plane SDK scaffolding is only for TypeSpec project. But this is a swagger project, and the swagger have existed for a long time, but it does not generate .NET SDK. We cannot identify it is a green field service or brown field service.

We need to decide if we need to support scaffolding for this kind of project. If not, .NET automation will throw an error for this, skip the generation.

@chunyu3 ok, this is the change needs to make in .NET automation script. What is the other issue you mentioned above for the SDK automation framework? Does it still exist?

@chunyu3 ok, this is the change needs to make in .NET automation script. What is the other issue you mentioned above for the SDK automation framework? Does it still exist?

@raych1 The issue is because mgmt-plane will not support scaffolding for swagger project. So we will throw error if it is a swagger project but it is a new PR (no sdk package folder), and the whole .NET sdk automation still fail.

The automation framework issue does not exist.