There's a disparity between how Certificate management is accessed in WinBox vs. CLI:
CLI: /certificate (n.b. "certificate", singular)
Winbox: System -> Certificates (plural, and underneath /System)
It's hardly fatal, but I do somewhat often find myself tring to type /system/certificates at the CLI, or looking for Certificate at the top level in Winbox. Which of course don't work.
Is there a justification for why the two UIs have these different paths (and even slightly different name, certificate vs certificates)? Or is it Just One Of Those MikroTik Things?
I propose that at the CLI certificate management should move under /system/certificate and there should be an alias as /certificate to avoid breaking existing scripts. This would allow consistency going forward and provide an eventual migration path to a single, consistent way to access certificate management.
(Of course, it could also be done that certificate management move in the WinBox GUI to the top level, but that might clutter the WinBox top level menu. That's why I made the proposal in the sense that I did).