GomathiselviS
recheck
> 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 >...
> 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"...
> 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...
@rohitthakur2590 Can you please look into this?
@ryanmerolle Can you please try "diff_against: session" and "diff_against: running" ? These options, do the diffs after applying the intended_config. Please let me know if these options work as you...
@ryanmerolle Please add `wait_for_connection` task in between the `RELOAD DEVICE` and `RESET CONNECTION` tasks. `wait_for_connection` waits until the device is in usable state and then proceeds with the following tasks.
@IPvSean From what I tested on a local vm, once we give reload now command, it takes a few seconds to actually start rebooting. The reset connection task gets executed...
Hi @jhg03a , Can you please provide the running-config from the device, when you tried the above-mentioned playbook?