BIND 10 #3028: Cmdctl print_settings - conflict between behavior and help documentation
BIND 10 Development
do-not-reply at isc.org
Mon Aug 19 11:28:26 UTC 2013
#3028: Cmdctl print_settings - conflict between behavior and help documentation
-------------------------------------+-------------------------------------
Reporter: bconry | Owner: muks
Type: defect | Status:
Priority: medium | reviewing
Component: Unclassified | Milestone:
Keywords: | Sprint-20130820
Sensitive: 0 | Resolution:
Sub-Project: Core | CVSS Scoring:
Estimated Difficulty: 2 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => muks
Comment:
Hello
Replying to [comment:7 muks]:
> * Just remove it altogether (other commands like `shutdown` won't work
without being handled in cmdctl). Also remove the commented line in
`b10-cmdctl.xml`.
I did something similar. Now I use the shutdown command for the test.
What comment line do you mean? I can't seem to find one.
> * Put it in a derived class `MyCommandControl` that exists in
`cmdctl_test.py` that calls `super()` for all other commands except
`test_command`.
That would make little sense. We would be testing that the derived class
works and we wouldn't enter the real code in that test at all.
Proposed changelog:
{{{
[func] vorner
The CmdCtl's command "print_settings" was removed. It served no real
purpose
and was just experimental leftover from early development.
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/3028#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list