Bug #4114
Exclude command groups if they are not set by kamaki or users
| Status: | Closed | Start date: | 07/08/2013 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | 07/08/2013 | |
| Assignee: | Stavros Sachtouris | % Done: | 100% |
|
| Category: | kamaki | Spent time: | - | |
| Target version: | v0.10 | Estimated time: | 2.00 hours |
Description
This report addresses a special case of a command python package with multiple command group specifications, where some of them are to be included in the session and some others are to be excluded.
For example, the cyclades CLI specification contains many command groups, e.g. server, network and floatingip. The later is a new command group and is hidden/optional for the time being.
The problem: Since most of the cyclades command specifications are internally requested by kamaki CLI, the cyclades spec package is loaded with all its command groups.
The sollution: exclude the non-requested command groups while loading the command spec package.
Associated revisions
Exclude unset optional cmd groups
Refs: #4114
E.g. the cyclades spec package contains the non-optional group "server" and
the optional group "floatingip". Now kamaki can load only the "server"
group, except if the user requests the loading of "floatingip" group too.
Update Changelog optional cmd spec bug fix
Refs: #4114
History
#1 Updated by Stavros Sachtouris over 10 years ago
- Status changed from Resolved to Closed