[tsp-client] The output of the tsp compile command should be logged using the Logger

[raych1]

Description
The output while calling the SDK emitter in tsp-client is currently only displayed in the console. For better troubleshooting, this output should also be emitted to the Logger so that it can be displayed in the pipeline scenario.

This is the code location:

azure-sdk-tools/tools/tsp-client/src/typespec.ts

Line 112 in eaa42a7

console.error(

//CC: @catalinaperalta @chunyu3

[chunyu3]

Hello @catalinaperalta in .NET generator we will log some information, but when tsp-client execute .Net emitter, the logs of .NET emitter are missing.

When I run local, it can see the logs, but when run in ci pipeline, the logs are missing

[catalinaperalta]

Hi all, I opened a PR addressing this yesterday, waiting on a review then will release a tsp-client update. Feel free to add your own review on the PR as well :)

[catalinaperalta]

v0.9.1 of tsp-client was released and is now printing the diagnostics with the logger. Please update to that version and give it a try. Thanks

[catalinaperalta]

@raych1 the output of the diagnostics causes a lot of noise when generating using tsp-client. Any issues if I log them at the debug level? I think you're already using the --debug flag in the pipeline, right?