5010e56223
Pipfile.lock: Run pipenv update
...
Ansible 2.9.2
2019-12-08 12:28:54 +02:00
5162e21b86
Pipfile.lock: Re-install with Python 3.8
2019-11-17 11:26:10 +02:00
48a9acadd9
Pipfile.lock: Run pipenv update
...
Brings Ansible 2.9.0 and others.
See: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst
See: https://docs.ansible.com/ansible/2.9/porting_guides/porting_guide_2.9.html
2019-11-04 10:08:17 +02:00
ebfdc7968c
Pipfile.lock: Run pipenv update
2019-10-26 16:00:46 +02:00
240b0c5954
Pipfile.lock: Run pipenv update
...
Brings Ansible 2.8.5, among other things.
2019-09-13 22:17:38 +03:00
d46c64ca29
Run pipenv update
2019-07-06 21:15:34 +03:00
4f1d413477
Pipfile.lock: Run pipenv update
2019-06-08 23:19:35 +03:00
ea936673d9
Pipfile.lock: Run pipenv update
2019-05-08 09:16:28 +03:00
dee90ed4bc
Run pipenv update
2019-03-17 17:12:27 +02:00
9dc3396544
Pipfile.lock: run pipenv update
2019-03-13 12:36:30 +02:00
3e1eddd4b8
Pipfile.lock: run pipenv update
2019-02-26 11:24:34 -08:00
bc88e05aa5
Pipfile.lock: Run pipenv update
2019-01-28 14:02:12 +02:00
a4fe3698e8
pipenv update
2019-01-10 08:07:09 +02:00
bdf0a19493
Pipfile.lock: pipenv update
2018-12-02 22:30:47 +02:00
9b8662eb34
Pipfile.lock: Run pipenv update
...
Ansible 2.7.1
2018-10-28 08:35:55 +02:00
484ea053cf
Re-create pipenv with Python 3.7 and reinstall packages
2018-10-25 12:01:30 +03:00
6eb6ab3070
Pipfile.lock: pipenv update
2018-10-11 08:17:02 +03:00
3006536e86
Update pipenv
...
Use Python 3.7 and run pipenv update to lock latest packages.
2018-08-29 09:09:26 +03:00
5d9577bc2d
Pipfile.lock: Run pipenv update
2018-07-29 16:13:43 +03:00
4f6d02922a
Run pipenv update and pipenv sync
2018-07-23 13:10:39 +03:00
9dfc0a2f1c
Pipfile: Pin Ansible < 2.6
...
I haven't tested Ansible 2.6 yet.
See: https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst
See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.6.html
2018-07-01 12:00:52 +03:00
37a7ff4e72
Pipfile.lock: Run pipenv update
2018-06-24 08:59:33 +03:00
533b9c60e7
Use ansible >= 2.5.1 for pipenv
2018-05-18 17:35:07 +03:00
d4a0dab704
Add netaddr to pipenv configuration
...
Required by the ansible-relayor role.
2018-05-07 11:04:22 +03:00
436e823415
Update Ansible to 2.5.2 in pipenv
2018-04-29 11:41:24 +03:00
c77167fc17
Pipfile: Use Ansible 2.5.1
...
I had been using this from the stable-2.5 branch for a few weeks in
order to work around some issues with Jinja2 and ansible-vault, but
now that version 2.5.1 has been released I can use it directly from
pip.
2018-04-23 13:45:21 +03:00
fb1573922c
pipenv lock
2018-04-10 11:09:13 +03:00
933cbfd51c
Rework pipenv
...
Ansible 2.5.0 currently has problems with Jinja2 expressions and vaults
so I decided to use Ansible from a source checkout of the devel branch.
I removed the old Pipfile and re-created it with Python 2 and satisfied
the dependencies from requirements.txt, then sourced Ansible:
$ rm Pipfile*
$ pipenv install --two -r ~/src/git/ansible/requirements.txt
$ pipenv shell
$ source ~/src/git/ansible/hacking/env-setup
2018-04-05 12:14:46 +03:00
aab49ca9d7
Update pip modules
2018-03-26 15:54:53 +03:00
8adc1cb3bb
Use ansible 2.5.0rc3
2018-03-21 20:52:45 +02:00
9296d78361
Pipfile.lock: Run pipenv update
2018-03-16 10:35:28 +02:00
b2566f27c0
Use Python 3 for Pipenv
2018-03-08 01:03:14 +02:00
67c4320607
Add files for pipenv support
...
Pipenv is a new way to do Python virtual environments. I created the
virtual environment here using:
$ pipenv --two
$ pipenv install ansible ansible-lint
To use the virtual environment you enter the project directory and
type:
$ pipenv shell
See: https://github.com/pypa/pipenv
2018-01-28 10:56:06 +02:00
