You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ansible/hacking
Matt Clay 7842b99106 Make ansible-test available in the bin directory. (#45876)
(cherry picked from commit f3d1f9544b)
6 years ago
..
aws_config sns_topic boto3 port (#39292) 6 years ago
tests Facts distribution clear linux 31501 (#32453) 7 years ago
ticket_stubs 2.6 changelog gen/version/root dir cleanup (#40421) 7 years ago
README.md 2.6 changelog gen/version/root dir cleanup (#40421) 7 years ago
ansible_profile start of 'profiling utils' 8 years ago
env-setup Make ansible-test available in the bin directory. (#45876) 6 years ago
env-setup.fish Make ansible-test available in the bin directory. (#45876) 6 years ago
fix_test_syntax.py Fix shebangs and file modes and update tests. (#40563) 7 years ago
get_library.py Surround top-level function and class definitions with two blank lines. 6 years ago
metadata-tool.py Use https for links to ansible.com domains. 7 years ago
report.py Replace exit() with sys.exit() 7 years ago
return_skeleton_generator.py Use JSON returns values to create RETURN docs 7 years ago
test-module Remove use of simplejson throughout code base (#43548) 6 years ago
update_bundled.py Update additional pypi.python.org URLs to pypi.org (#41373) 7 years ago

README.md

'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/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 -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.

fix_test_syntax.py

A script to assist in the conversion for tests using filter syntax to proper jinja test syntax. This script has been used to convert all of the Ansible integration tests to the correct format for the 2.5 release. There are a few limitations documented, and all changes made by this script should be evaluated for correctness before executing the modified playbooks.