Commit Graph

55 Commits

Author SHA1 Message Date
5e918da88e
Pipfile.lock: run pipenv update 2021-09-05 15:38:51 +03:00
7b233eb31d
Pipfile.lock: Run pipenv update
Ansible 4.3.0
2021-08-01 16:14:42 +03:00
681be5eb19
Pipfile.lock: run pipenv update
Ansible 4.2.0 and Ansible Core 2.11.2
2021-07-01 18:11:11 +03:00
1d5db7bdbe
Pipfile.lock: run pipenv update 2021-06-13 16:14:05 +03:00
32da3a3341
Pipfile.lock: Re-create pipenv environment for Ansible 4.0.0
Seems we need to manually uninstall and re-install.
2021-05-20 10:21:01 +03:00
3e7130b519
Pipfile.lock: run pipenv update 2021-05-14 13:56:56 +03:00
7145298f90
Pipfile.lock: Run pipenv update 2021-05-10 15:59:34 +03:00
1bfd2bc441
Pipfile.lock: Run pipenv update
Ansible 3.3.0
2021-04-28 12:49:23 +03:00
d3978e5b07
Pipfile.lock: run pipenv update 2021-04-13 14:28:34 +03:00
9c36cfb8e5
Pipfile.lock: Run pipenv update 2021-03-19 13:18:19 +02:00
6e96d48ea6
Pipfile.lock: Run pipenv update
Ansible 3.0.0
2021-03-01 15:27:58 +02:00
8cb232a765
Pipfile.lock: Run pipenv update 2021-02-07 15:53:10 +02:00
d4ca119265
Pipfile.lock: run pipenv update
Minor Ansible update
2021-01-27 11:06:12 +02:00
10b6b11be5
Pipfile.lock: Run pipenv update 2020-12-22 15:35:26 +02:00
d553f80a00
Run pipenv update 2020-12-09 22:47:44 +02:00
08ae79ae88
Use Python 3.9 in pipenv setup 2020-12-02 11:33:10 +02:00
776fd7cc76
Pipfile.lock: Update dependencies with pipenv update 2020-11-29 10:31:13 +02:00
31ffda5466
Re-create Pipfile
Something about upgrading from Ansible 2.9 to 2.10 wasn't working.
2020-11-01 19:04:07 +02:00
d3c2b0559a
Pipfile.lock: Run pipenv update
Ansible 2.9.13
2020-09-02 15:31:01 +03:00
f4da35acee
Pipfile.lock: Run pipenv update
Ansible 2.9.10
2020-06-25 20:56:18 +03:00
0e0c21bd16
Pipfile.lock: Run pipenv update
Brings Ansible 2.9.2.
2020-04-24 11:27:35 +03:00
4eb94d9127
Pipfile.lock: Run pipenv update
Ansible 2.9.6 and other minor updates to dependencies.
2020-03-16 17:56:19 +02:00
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