Dwarakanath Yadavalli

@mirceaulinic As with any technology area, priorities are assessed continuously. The focus is always on what is used by the customers and is important to them. There is a fine...

@mirceaulinic Thanks for the patience. We are debating this internally and will share the feedback/decisions once available. We may reach out to you in the case of any clarification.

We will evaluate it and get back.

@sadsfae Please send a pull request

or how about ``` yml interfaces_terse: - category: critical - command: show interfaces terse - item: xpath: //physical-interface interfaces_terse: - category: major - command: show version - item: ```

@titusfoo The module approach would definitely give you more control as you can build contexts within your code.

@titusfoo We will evaluate this and check if a generic two-way diff can be implemented. Thank you.

To have an option to validate the syntax of the test file. More than just checking the yaml. Similar/close to ansible-playbook xxx.yml --syntax-check

@psagrera Please check the usage of 'ancestor' in XPATH. It needs to be specific to a given XPATH. For example refer: http://stackoverflow.com/questions/3005370/xpath-to-find-nearest-ancestor-element-that-contains-an-element-that-has-an-attr

Which version of Junos are you using on EX2200 and 3300?