Why GenerateCurlCommand with debug

[eatmeatball]

I require the GenerateCurlCommand function to log information, but I do not wish to include any debug-related output. Previously, I had written a function named restyResult2curl, but in the newer version, I discovered the GenerateCurlCommand. However, recently, GenerateCurlCommand underwent changes. Specifically, the EnableTrace() method is no longer available, and setting the debug level results in excessive output.
😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠

[jeevatkm]

@eatmeatball Thanks for reaching out.

That change happened as part of this: #828. Typically, the trace feature is used in production to capture metrics. Plus, users enable debugging with consideration for lower environments, reducing the risk to lower environments around secret leaks.

Let me know if you have any thoughts about redesigning the options. If it's feasible, I will consider it for the upcoming release, v3.

[jeevatkm]

@eatmeatball I'm awaiting your feedback.

[jeevatkm]

@eatmeatball I thought about it. I already did two changes in the minor version. So I will make generate curl cmd option independent in the upcoming v3 as a behavior change.

[jeevatkm]

Done.