Ryan Merolle

Should I just close this out given my findings are as expected? I am sort of lost because fact_diff with | ansible.utils.to_paths does not output anything that is human readable...

The feature did not seem to work for me it fails: ``` - name: VALIDATE CONFIGS arista.eos.eos_config: intended_config: "hostname foo" diff_against: validate_config check_mode: True diff: true register: validate_config ``` ```...

So by pulling your latest commit the example below works for both httpapi & network_cli: ```yaml - name: VALIDATE CONFIGS arista.eos.eos_config: intended_config: "hostname foo" diff_against: validate_config check_mode: True diff: true...

on a separate note, this is useful for applying new config, but would there also be a way to replace the config. IE the way it works above so far...

First of all @GomathiselviS thanks for all the hard work. Its on me for not articulating the feature request well. Your current approach is a valid part of the feature,...

@GomathiselviS Here is the approach I recommend: For `eos_config`, if `check_mode: True`, run the command `show session-config` before aborting the session. Store this output in the result var with a...

@rohitthakur2590 let me know how we can sync up and reset on this issue and PR. Thanks!

@rohitthakur2590 This still does not take a full config, (ie replace: config) and validate that it. Is that coming in another PR?

Ah thanks for the clarification. Tag me for that and I will test accordingly.

Looking further into the module, the after is not actually applied to the device, hence the behavior. This is likely by design, but still not idea. This module seems to...