pip: use latest instead of upgrade

I'm not sure if this is clearer or not (which is why I proposed it
separately here).

From inspection of the code, adding "state: latest" just means Ansible
runs "install -U" ... which is pretty much the same thing as adding
--upgrade.  Which is clearer, I'm not sure?

Change-Id: I6e31523686555e33d062f3b05f2385d7e21e2620
Ian Wienand 4 months ago
parent 4fa8d2dd39
commit c921954649
No known key found for this signature in database

@ -49,6 +49,6 @@
when: _venv_requirements_txt.changed
requirements: '{{ create_venv_path }}/requirements-venv.txt'
extra_args: '--upgrade'
state: latest
virtualenv: '{{ create_venv_path }}'
virtualenv_command: '/usr/bin/python3 -m venv'

@ -67,10 +67,10 @@
when: _requirements_updated.changed
requirements: '/usr/ansible-venv/requirements.txt'
virtualenv: '/usr/ansible-venv'
# Always upgrade because only called in response to
# requirements.txt changes.
extra_args: '--upgrade'
state: latest
virtualenv: '/usr/ansible-venv'
# From Ansible 2.10 >= most of the fun stuff is in collections. Clone
# our required collections here. Note this is only for our testing of