@Apachez , @gaige Hello Guys!
How do we want to continue here, please?

Are you able to update the status of this Mafifest, add a link to a new PR or other doc please?
Thank you

Are you able to update the status of this Mafifest, add a link to PR or other doc please?
Thank you

Are you able to update the status of this Mafifest, add a link to PR or other doc please?
Thank you

Thank you for the question.
The latest supported Ansible core version for this collection is 2.18.2
2.19+ unfortunately has a lot of changes that require the code rework, most notably, the community collections we use alongside with ours are not compatible as well (e.g. ansible.netcommon).
There is an issue https://github.com/vyos/vyos.vyos/issues/417 lodged to embrace 2.19+ at some point, but right now we have to wait for the adoption of this version by wider user base.

@Viacheslav @badger42 hi Guys! Why is this in the Ansible FR section?

Hi @evgmol, nice one, thanks.

@lingfish hi!
Sorry for taking so long

Hi, yeah oops, should have mentioned that!

https://github.com/vyos/vyos.vyos/pull/437 — merged now. Can we close the task?

@lingfish Hi!
Which module are you using?

https://github.com/vyos/vyos.vyos/pull/430 is merged.

Work is here https://github.com/vyos/vyos.vyos/pull/433

The feature is really missing - I raised a PR to work on it https://github.com/vyos/vyos.vyos/pull/433

The feature is available in the latest Galaxy collection
https://galaxy.ansible.com/ui/repo/published/vyos/vyos/content/module/vyos_l3_interfaces/

More in Slack https://vyos-community.slack.com/archives/C027BSYGHPT/p1754577533265449
In general:

@nicolasberens hi!

I am working here on this use case https://github.com/vyos/vyos.vyos/pull/429

• name: BackUp Cuideo router's config hosts: CUIDEO_ROUTERS

@nicolasberens Raising PR https://github.com/vyos/vyos.vyos/pull/430 to make vyos_config and cliconf less greedy

Hi @nicolasberens
That is interesting - when I use rule 5 for example - there is also no change

Additional details from Slack:
it is not only 1st run. He runs his playbook for 3 routers. Only one works without problems. He says that the configs are the same and the version is - 1.4.3.
Ansible verbose info

@a.apostoliuk hi!
Can we have:

Hello @nicolasberens
Apologies for this taking too long to respond.
I investigated further and found that community module function netcommon.CliConf inserts an extra space, thus breaking the long lines and causing diff to generate, which, in turns, impacts the idempotency of the VyOS modules.

Yes, i want to delete and recreate it. But it needs to be in the same step, not in 2 separate ones.
With 2 Seperate ones, you delete the group, commit it, then recreate and commit it again.
In a single step, you delete the group, recreate it and then commit. That way the group itself will always exist.

So, I tried a few approaches here - in particular, I coded logic to preserve 'set' commands if they are in running config and there is a corresponding 'delete' clause, to we do see 'delete' and 'set' commands in the config to compare.
Despite this, the Ansible connnection.get_diff does not work with this well, as it tends to remove 'delete' from the resultant set as not making sense (it kind of being over-smart here)

That is clear now, thanks @nicolasberens
(Sorry, I must have misspelled your username)

@evgmol did you want to tag me?

@nicholaschaffeee Hi!
Are you able to describe your use case above?

As an example (and the reason why i try to solve this issue the way i am doing it right now), the junos module (https://docs.ansible.com/ansible/latest/collections/junipernetworks/junos/junos_config_module.html#ansible-collections-junipernetworks-junos-junos-config-module) support this exact behaviour. So it was easy to adapt this for our vyos firewalls.

It seems that community plugin netcommon network_cli breaks long lines resulting in diff. I tried ansible_terminal_width but no luck
I will be looking for some workarounds, unless there is already an open issue with Netcommon

I can see the community module we use (necommon/network_cli) actually returns the running config with a broken long strings - it inserts extra space

Hi,
I am testing against 1.4.2, via pylibssh, - I see 4096-long one does break idempotency but I see no Exception
I will retest with vyos_user

Looking at vyos.vyos.vyos_firewall_global, i have a few issues with it:

Using this playbook i can reproduce the same bug with the vyos_user command (2048 does not change on the second run, 4096 does):

@nicolasberens You may want to give the vyos_user command a try as it should deal with this appropriately.

I think this may be related to the other T7621, since they would both involve the diff engine for the cliconf plugin.

Hi,
thanks for the reply.

Hi @nicolasberens!
I believe the module is configured to match line by line by default and only work out on deltas in the config.
So if in the active Ansible session, the module does not sense changes after 'delete' (because there are none as yet, since the command is not applied) - At start, the module retrieves the current configuration and process it, then issues a set of commands.
Either having two separate tasks to delete first, then to set works, or the example below also works.

Hi All,
Looking into this

Doesn't this feature exist in 1.5?

In T7474#225365, @badger42 wrote:

I am not a developer, so not sure how to implement this. This is a request for new functionality.

I am not a developer, so not sure how to implement this. This is a request for new functionality.

There is a repo for VRRP https://github.com/acassen/keepalived that we use
So it it necessary to understand how it looks like natively for keeplived before it can be implemented

@Viacheslav Unfortunately, I don't know how to implement this.

Closed out by https://github.com/vyos/vyos.vyos/pull/392

Closed with changes ini PR#397

Send a real example from keepalived if you know how to implement this

You should use policy route
it is not cisco

Add example for rsyslog
It is not cisco