Config nodes containing spaces which have sub-nodes don't work
Open, NormalPublic


Config nodes that can contain spaces and have sub-nodes end up not working correctly. For instance L2TP and PPTP usernames, and SNMP community string. setLevel in ends up not working in that circumstance, which makes the sub-nodes not function. SNMP in that case ends up with an invalid snmpd.conf. L2TP and PPTP users end up with a blank password.


Difficulty level
Normal (likely a few hours)

Worse, such config can be saved, but cannot be loaded afterwards because the formatter doesn't bother to quote such strings and you end up with a syntactically invalid config.

I'm afraid there may not be a general solution in 1.x.x, but we can identify tag nodes without validation rules and add some rules to them at least.

syncer triaged this task as Normal priority.Aug 1 2017, 4:10 AM
syncer changed the edit policy from "Task Author" to "Custom Policy".
syncer edited projects, added VyOS 1.2.x; removed VyOS 1.1.x.
syncer set Version to -.
syncer removed syncer as the assignee of this task.
syncer edited subscribers, added: Maintainers, Core Community, Community; removed: dmbaturin.
syncer added a subscriber: syncer.

Do we need to create sub-task per component?