6b94bdb78d
In reviews for I3696740112fa691d1700040b557f53f6721393e7 clarkb correctly pointed out that a constraint like ansible<8 will never result in the production venv being updated. The point of having the requirements.txt was to avoid a full update run on the venv on every one of its frequent runs. A good in-between seems to be writing out the current day timestamp into the requirements file. Since the template: return value is based on comparing the hash of the old/new (we suspected this, but I also double confirmed with a local test), this results in the template being updated just once a day. Ergo we will run a --update run on the ansible-venv just once a day. Change-Id: I78a914f71cef687f09fcfee0f3f498b79d810f5d
5 lines
104 B
Django/Jinja
5 lines
104 B
Django/Jinja
# Update timestamp: {{ _date.stdout }}
|
|
{% for r in install_ansible_requirements %}
|
|
{{ r }}
|
|
{% endfor %}
|