[
https://issues.apache.org/jira/browse/CLOUDSTACK-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav resolved CLOUDSTACK-1037.
-------------------------------------
Resolution: Fixed
All major features fixed.
Moving following good to have features to a new ticket;
- Theme-ing support for pygment based colored output
- Fix fuzzy param completion to a much better implementation
- Scope for unicode and zsh/bash autocompletion
> Make cloudmonkey awesome-er: Online help docs and api discovery, better
> colored output, parameter value autocompletion
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1037
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1037
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Make cloudmonkey awesome-er;
> - Get rid of marvin dependency, check against avaiable precache
> - After fixing apidocs, make it have a failsafe precache
> - Implement protocol to discover apis for a user, using the ApiDiscovery
> plugin; on failure use the failsafe precache bundled within cloudmonkey
> - Change config file system strucuture, rework the arch such that plugins can
> be developed for cloudmonkey for testing, colored output etc.
> - Implement better coloring and maybe html output (who knows one may use that
> to share outputs via websites :) use Pygments and have scope for themes
> (don't impose author's fav. color scheme on users)
> - Have auto-completion (network/mgmt server load heavy) for parameter values
> - Rework functional closures and shell input handling such that it's
> maintainable and can bear long release cycles alongwith CloudStack
> - Scope for unicode and zsh/bash autocompletion (good to have, may not be
> possible in given timeframe)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
