Adding Diagnosis command to cli - #415
Conversation
|
@dashbhanu, I have to say that I'm having issues with the basic design of this functionality. There's a lot I think we need to modify, so I'm starting from some of the most significant points: Reading plain text (not formatted) response and then parsing it manually, is something we really want to avoid. I don't think that the code should be included as part of the jfrog-client-go library, because I find it hard it believe that it is useful for other applications - at least they way the API is built now. There's a lot more to discuss, in terms of where the info files should be saved to, how the command should receive them, code styling and more, but I suggest we start with the above first. Thanks |
|
Thank you @eyalbe4 for your time, I will take some more time and go throw your review comments and then again resubmit PR. Thanks |
|
@dashbhanu, |
|
Closing this one for now. |
build-info-go's NuGet FlexPack work landed on main as b325d34 (squash of PR #415), so the branch pseudo-version is no longer needed. Also bumps jfrog-cli-artifactory to caf4135, which makes the same change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A new features in CLI to get a diagnosis of Artifactory after each upgrade. This command should run before and after upgrade, so that it will print the performance and stability of artifactory instance. The default command is like
jfrog rt diagnosis