ansible_managed vaule has changed and I can't work out why

[mike _]

I've been using Ansible as a clone of the git repo, periodically checking out newer stable branches. I'm currently using the stable-2.8 branch but looking to move to a newer version.

The splitting of Ansible in to parts makes me think the best way to use the latest version  is  start over with a new Ansible install, so I've installed Ansible as described at https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-in-a-virtual-environment-with-pip

It seems to work fine, except the value of the {file} part of the ansible_managed string has changed. With 2.8 {file} is expanded to the full path of the template, as described at https://docs.ansible.com/ansible/2.4/intro_configuration.html#ansible-managed

With the latest version of Ansible, it's just the filename. So ansible_managed has gone from

# Ansible managed, do not edit directly: /home/mike/blah/roles/core/templates/bash_prompt.sh.j2 by mike on foo

to 

# Ansible managed, do not edit directly: bash_prompt.sh.j2 by mike on foo

It this expected behaviour?

I didn't see anything in release notes about this when I looked  and I cannot find anything in the documentation for the current version of Ansible which explains what the value of {file} is supposed to be as https://docs.ansible.com/ansible/2.4/intro_configuration.html#ansible-managed does.

thanks,

mike

[Brian Coca]

This was a bugfix, since it would cause the template to be 'changed'
if 2 diff users executed (path would reflect joe's home dir) so we
preserve the 'relative path' and avoid unneeded updates.


--
----------
Brian Coca