mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
e238ae999b
Make pyca/cryptography the preferred backend for cryptographic needs (mainly vault) falling back to pycrypto
pyca/cryptography is already implicitly a dependency in many cases
through paramiko (2.0+) as well as the new openssl_publickey module,
which requires pyOpenSSL 16.0+. Additionally, pyca/cryptography is
an optional dep for better performance with vault already.
This commit leverages cryptography's padding, constant time comparisons,
and CBC/CTR modes to reduce the amount of code ansible needs to
maintain.
* Handle wrong password given for VaultAES format
* Do not display deprecation warning for cryptography on python-2.6
* Namespace all of the pycrypto imports and always import them
Makes unittests better and the code less likely to get stupid mistakes
(like using HMAC from cryptogrpahy when the one from pycrypto is needed)
* Add back in atfork since we need pycrypto to reinitialize its RNG just in case we're being used with old paramiko
* contrib/inventory/gce: Remove spurious require on pycrypto
(cherry picked from commit 9e16b9db275263b3ea8d1b124966fdebfc9ab271)
* Add cryptography to ec2_win_password module requirements
* Fix python3 bug which would pass text strings to a function which
requires byte strings.
* Attempt to add pycrypto version to setup deps
* Change hacking README for dual pycrypto/cryptography
* update dependencies for various CI scripts
* additional CI dockerfile/script updates
* add paramiko to the windows and sanity requirement set
This is needed because ansible lists it as a requirement. Previously
the missing dep wasn't enforced, but cryptography imports pkg_resources
so you can't ignore a requirement any more
* Add integration test cases for old vault and for wrong passwords
* helper script for manual testing of pycrypto/cryptography
* Skip the pycrypto tests so that users without it installed can still run the unittests
* Run unittests for vault with both cryptography and pycrypto backend
64 lines
1.6 KiB
Markdown
64 lines
1.6 KiB
Markdown
'Hacking' directory tools
|
|
=========================
|
|
|
|
Env-setup
|
|
---------
|
|
|
|
The 'env-setup' script modifies your environment to allow you to run
|
|
ansible from a git checkout using python 2.6+. (You may not use
|
|
python 3 at this time).
|
|
|
|
First, set up your environment to run from the checkout:
|
|
|
|
$ source ./hacking/env-setup
|
|
|
|
You will need some basic prerequisites installed. If you do not already have them
|
|
and do not wish to install them from your operating system package manager, you
|
|
can install them from pip
|
|
|
|
$ easy_install pip # if pip is not already available
|
|
$ pip install -r requirements.txt
|
|
|
|
From there, follow ansible instructions on docs.ansible.com as normal.
|
|
|
|
Test-module
|
|
-----------
|
|
|
|
'test-module' is a simple program that allows module developers (or testers) to run
|
|
a module outside of the ansible program, locally, on the current machine.
|
|
|
|
Example:
|
|
|
|
$ ./hacking/test-module -m lib/ansible/modules/commands/shell -a "echo hi"
|
|
|
|
This is a good way to insert a breakpoint into a module, for instance.
|
|
|
|
For more complex arguments such as the following yaml:
|
|
|
|
```yaml
|
|
parent:
|
|
child:
|
|
- item: first
|
|
val: foo
|
|
- item: second
|
|
val: boo
|
|
```
|
|
|
|
Use:
|
|
|
|
$ ./hacking/test-module -m module \
|
|
-a "{"parent": {"child": [{"item": "first", "val": "foo"}, {"item": "second", "val": "bar"}]}}"
|
|
|
|
Module-formatter
|
|
----------------
|
|
|
|
The module formatter is a script used to generate manpages and online
|
|
module documentation. This is used by the system makefiles and rarely
|
|
needs to be run directly.
|
|
|
|
Authors
|
|
-------
|
|
'authors' is a simple script that generates a list of everyone who has
|
|
contributed code to the ansible repository.
|
|
|
|
|