ansible/hacking
Matt Martz 49eb53b44d
pylint plugin to catch due/past-due deprecated calls (#44143)
* Start of work on pylint plugin to catch due/past-due deprecated calls

* Improve deprecated pylint plugin

* Catch call to AnsibleModule.deprecate also

* Skip splatted kwargs, we can't infer that info

* Add error for invalid version in deprecation

* Skip version if it's a reference to a var

* Disable ansible-deprecated-no-version for displaying deprecated module info

* fix comments

* is None

* Force specifying a version, this can be disabled on a per case basis

* Disable ansible-deprecated-version by default

* Remove to look for 2.8 deprecated

* Revert "Remove to look for 2.8 deprecated"

This reverts commit 4e84034fd1.

* Add script and template used for creating issues for deprecated issues

* Fix underscore var
2018-09-25 10:31:41 -05:00
..
aws_config Improve iam_group exception handling (#45599) 2018-09-17 19:53:44 -04:00
tests Facts distribution clear linux 31501 (#32453) 2018-01-20 15:05:53 -05:00
ticket_stubs Add a ticket stub for guiding GitHub newcomers 2018-09-11 17:51:54 +02:00
ansible_profile start of 'profiling utils' 2017-05-31 14:00:12 -04:00
create_deprecated_issues.py pylint plugin to catch due/past-due deprecated calls (#44143) 2018-09-25 10:31:41 -05:00
deprecated_issue_template.md pylint plugin to catch due/past-due deprecated calls (#44143) 2018-09-25 10:31:41 -05:00
env-setup Make ansible-test available in the bin directory. (#45876) 2018-09-19 17:58:55 -07:00
env-setup.fish Make ansible-test available in the bin directory. (#45876) 2018-09-19 17:58:55 -07:00
fix_test_syntax.py Fix shebangs and file modes and update tests. (#40563) 2018-05-22 14:25:36 -07:00
get_library.py Surround top-level function and class definitions with two blank lines. 2018-07-31 12:06:56 -07:00
metadata-tool.py Use https for links to ansible.com domains. 2018-04-23 11:33:56 -07:00
README.md 2.6 changelog gen/version/root dir cleanup (#40421) 2018-05-21 16:14:53 -07:00
report.py Don't require requests in hacking/report.py (#45350) 2018-09-07 11:51:41 -05:00
return_skeleton_generator.py Use JSON returns values to create RETURN docs 2017-09-11 14:33:11 -07:00
test-module Remove use of simplejson throughout code base (#43548) 2018-08-10 11:13:29 -05:00
update_bundled.py Update additional pypi.python.org URLs to pypi.org (#41373) 2018-06-17 14:01:18 +02:00

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