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
Install and configure Ansible on a host via pip
This will install ansible into a virtualenv at
/usr/ansible-venv
Role Variables
A dictionary of configuration keys and their values for ARA's Ansible plugins.
Default configuration keys:
api_client: offline(can behttpfor sending to remote API servers)api_server: http://127.0.0.1:8000(has no effect when using offline)api_username: null(if required, an API username)api_password: null(if required, an API password)api_timeout: 30(the timeout on http requests)For a list of available configuration options, see the ARA documentation