ansible/hacking
2025-07-30 16:39:38 -07:00
..
azp Remove the yum module, redirect it to dnf (#81895) 2024-01-23 10:23:43 -06:00
backport Update triple single quotes to triple double quotes (#84099) 2024-10-09 21:22:35 +00:00
tests Require from __future__ import annotations (#81902) 2023-10-04 22:11:17 +00:00
ticket_stubs Add ticket stub for minor changes (#85350) 2025-06-18 17:05:23 -07:00
ansible-profile.py Cleanup the hacking directory a bit (#81960) 2023-10-11 17:44:42 -07:00
create-bulk-issues.py Improvements for the create-bulk-issues.py script (#84235) 2024-11-01 15:15:59 -07:00
deprecated_issue_template.md Add pymarkdown sanity test for core (#81220) 2023-07-11 14:40:47 -07:00
env-setup ansible-test - Remove generation of egg-info (#83786) 2024-08-14 09:03:51 -07:00
env-setup.fish Python binary should not be python at first try for env-setup.fish (#84212) 2024-11-05 16:13:52 +01:00
README.md Drop Python 3.11 controller support (#85590) 2025-07-30 16:39:38 -07:00
report.py Require from __future__ import annotations (#81902) 2023-10-04 22:11:17 +00:00
return_skeleton_generator.py Require from __future__ import annotations (#81902) 2023-10-04 22:11:17 +00:00
test-module.py Switch to stackwalk caller ID (#85095) 2025-05-05 18:00:02 -07:00
update-sanity-requirements.py ansible-test - Update venv management and sanity requirements (#83729) 2024-08-06 14:53:40 -07:00

'Hacking' directory tools

env-setup

The 'env-setup' script modifies your environment to allow you to run ansible from a git checkout using a supported Python version.

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

python -Im ensurepip  # if pip is not already available
pip install -r requirements.txt

From there, follow ansible instructions on docs.ansible.com as normal.

test-module.py

'test-module.py' 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.py -m lib/ansible/modules/command.py -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:

parent:
  child:
    - item: first
      val: foo
    - item: second
      val: boo

Use:

./hacking/test-module.py -m module \
  -a '{"parent": {"child": [{"item": "first", "val": "foo"}, {"item": "second", "val": "bar"}]}}'

return_skeleton_generator.py

return_skeleton_generator.py helps in generating the RETURNS section of a module. It takes JSON output of a module provided either as a file argument or via stdin.