# Ansible Software Baseline - Legacy Projects

**URL:** <https://forum.ansible.com/t/ansible-software-baseline-legacy-projects/27449>\
**Category:** Ansible Project\
**Created:** [May 4, 2018, 1:43am UTC](https://forum.ansible.com/t/ansible-software-baseline-legacy-projects/27449 "2018-05-04T01:43:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Stubbersfield](https://avatars.discourse-cdn.com/v4/letter/d/ec9cab/32.png) [@David\_Stubbersfield](https://forum.ansible.com/u/David_Stubbersfield)\
**Post date:** [May 4, 2018, 1:43am UTC](https://forum.ansible.com/t/ansible-software-baseline-legacy-projects/27449/1 "2018-05-04T01:43:16Z")

</div>

Hi,

I stumbled across the Ansible article below which is very relevant to a situation in my workplace; we have a need to configure server hosts in accordance with an approved software baseline (e.g. config.baseline file).

[https://www.ansible.com/blog/how-to-do-devops-without-leaving-legacy-behind](https://www.ansible.com/blog/how-to-do-devops-without-leaving-legacy-behind)

What I am unsure of is: what is Ansible best practice for associating a deployed baseline with a host?

What I thought about was adding a field in host\_vars/ like ‘baseline’ that is updated with the appropriate baseline version once an updated baseline has been deployed to a host.

Thanks in advance.

David.