meraki-cli icon indicating copy to clipboard operation
meraki-cli copied to clipboard

1.0.0+ Enhancement Requests and Known Bugs

Open PackeTsar opened this issue 4 years ago • 3 comments

Logging enhancement requests and known bugs here. If you have reported a bug or feature request and it is accepted as such, then it will show up here and your original issue will be closed.

PackeTsar avatar Feb 04 '21 04:02 PackeTsar

Enhancements

  1. Command tab-completion - argcomplete is already coded in. Just need working processes documented to enable in Windows, MacOS, and Linux.
  2. Multi-Execution Result Assembly - Multiple executions when piping produces multiple tables or JSON dumps instead of compiling everything into a single result. It is possible that the output of each of the results may be different. May want to compile results or have an option to do so. I suspect the current functionality would break if more than one pipe was used, but have not confirmed it.
    • UPDATE: This is confirmed. If trying to double pipeline doing something like meraki -f model:MS networks getNetworkDevices --networkId <networkId> | meraki -f "lldp:Meraki MV" switch getDeviceSwitchPortsStatuses | meraki switch updateDeviceSwitchPort --vlan 50, it breaks with a json.decoder.JSONDecodeError error. In order for double pipelining to work, results would have to be assembled. It also may be necessary to attach extra data to returned and assembled objects (like the serial of the switch that owns the port for the example command).
  3. Custom module insertion - Process result data, or retrieve source data through a custom Python module by inserting with something like -m mymodule.py
  4. CSV Integration - Enable outputting of items to CSV or reading from CSV for source data (similar to pipelining).
  5. Interactive Shell - Launch an interactive shell making it easier to use tab-completion or possibly some kind of DSL for scripting
  6. Upgrade notifications and native upgrade command
    • When the Meraki-CLI is run, it should try to run a check for a newer version and recommend an upgrade (if one is available). Similar to how the PIP library handles it.
    • The user should be able to invoke an upgrade from the tool itself. Something like meraki upgrade

PackeTsar avatar Feb 05 '21 16:02 PackeTsar

Bugs

PackeTsar avatar Feb 09 '21 16:02 PackeTsar

Documentation Fixes

PackeTsar avatar Feb 13 '21 05:02 PackeTsar