6f74fca238
* add new module: aws_stepfunctions_state_machine * add integration tests for new module: aws_stepfunctions_state_machine * fix sanity checks * use files/ folder instead for integration test * rename role name in integration test * attempt further permissions * iam states prefix * iam integration test prefix * add iam policy for running step functions state machine actions * slightly increase iam permission scope * rename integration test folder to proper name * move main() method to end of file * move contents of integration-policy.json for state machines to compute-policy.json * make check_mode return proper changed value + add check_mode integration tests * rename module to aws_step_functions_state_machine * fix missed rename in integration test variable * add purge_tags option * bump to version 2.10 |
5 years ago | |
|---|---|---|
| .. | ||
| aws_config | 5 years ago | |
| build_library | 5 years ago | |
| tests | 5 years ago | |
| ticket_stubs | 5 years ago | |
| README.md | 5 years ago | |
| ansible-profile | 5 years ago | |
| build-ansible.py | 5 years ago | |
| cgroup_perf_recap_graph.py | 6 years ago | |
| create_deprecated_issues.py | 6 years ago | |
| deprecated_issue_template.md | 6 years ago | |
| env-setup | 6 years ago | |
| env-setup.fish | 5 years ago | |
| fix_test_syntax.py | 7 years ago | |
| get_library.py | 6 years ago | |
| metadata-tool.py | 7 years ago | |
| report.py | 5 years ago | |
| return_skeleton_generator.py | 5 years ago | |
| test-module | 5 years ago | |
| test-module.py | 5 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.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/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.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.
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.