Martin Krizek
Martin Krizek
Duplicate of https://github.com/ansible/ansible/issues/71940
Related https://github.com/ansible/ansible/pull/71948
This has been fixed in `devel` in #56116 which is unlikely to be backported as it introduces a breaking change.
!waffling needs_revision
!waffling core_review
!waffling needs_revision
!waffling core_review
Use `follow: yes` if you want to operate on the real path instead of the symlink itself. Then `change` is correctly evaluated.
> Shouldn't --check still mimic normal behavior, with or without follow: yes ? I am not disputing that, just mentioning a 'safe' solution. ;-)