BIND 10 #3239: Configuring int value in quotes print funny error

[BIND 10 Development]

#3239: Configuring int value in quotes print funny error
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:  muks
                Type:  defect        |                       Status:
            Priority:  low           |  assigned
           Component:                |                    Milestone:
  configuration                      |  Sprint-20131015
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by muks):

 This was implemented (in `libb10-cc`) in the `trac3239` branch. But such
 an implicit conversion has introduced issues.

 There are places where the spec file accepts an integer in a string
 argument. If the string is automatically cast to integer type, the
 resulting value type mismatches the expected type from the spec file and
 fails.

 A different way to implement this would be to do the conversion in
 `bindctl` itself. But this is not something straighforward as bindctl uses
 Python's `json.loads()` method to parse a JSON parameter (it can be an
 integer, string, or a JSON tree structure). It does not do any type
 checking against a spec file and leaves it to `cfgmgr` when it actually
 sets the data.

 Another place to fix it is in `cfgmgr` where it validates the data against
 the spec file, but conversions have to be done in too many places. Besides
 the values are passed as-is to the config handlers of various components
 which automatically expect specific types.

 So I suggest it's best to resolve this ticket as "WONTFIX".

-- 
Ticket URL: <http://bind10.isc.org/ticket/3239#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development