If a change is made to remove this, I think it should be safely placed behind an explicit configuration parameter for the vyos_config

I believe the intent of the existing filters is to prevent accidental password changes. For an automation solution, I don't see significant value in changing this behavior, except to remove the plaintext variant as well. The intention here is to prevent accidental overwrite of passwords during the configuration step. The existing vyos_user should be used for handling password changes.

Yes, @GideonKuijt ; this is an intentional change to ansible-core from what I understand. They're trying to make the templating operations much more explicit, so some of the places where we were able to automatically have templating have been broken. Thanks for posting the solution here. I expect we'll see this in a few other places that have src: as well.

@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.

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

Closed with changes ini PR#397

@Apachez I believe @evgmol was referring to:

Module updates (6.0.0) add support for encrypted passwords, including idempotence and tests.

Given current state, I"m going to close this.

Starting work on this—seems relatively trivial for that particular item.

Resolved with latest changes for 6.0.0

Reportedly this problem did not exist in VyOS 1.5-rolling-202410260007 (according to slack with @evgmol ). I've seen the problem occur in versions as far back as Vyos-1.5-rolling-202411070006, so that may shed some light on where it occurs.

This turns out to be a simple fix. The problem is an issue with deleting directories on separate threads when running with multiple targets. Simple fix is to run_once: true the two places where this happens. Not surprisingly, this fix works.

Working on this one. The changes are more significant than I expected, partially due to address being plural now.

PR submitted

I've got a patch nearly ready

L3 tests working

Working in the branch, prepared for merge

The recent updates to vyos_user should support updating encrypted passwords, including appropriately understanding if there was a change.

@sdwilsh Unless you have an objection, I'm going to close this out as fixed by the current version in Main.

@sever should we move this to VyOS project instead of VyOS Ansible Collection, since the problem here was with 1.4.0?

Essential for release.

Essential for release

Important release test

1.4 and 1.5 working

Changes appear trivial enough I'm going to make them now

Needed before 6.0.0 release

vyos_config Integration tests under 1.4 and 1.5+ pass when run against each machine singly, so these changes may not be necessary to get integration tests running before the 6.0.0 release.

Being worked

Duplicate of existing PR