This AWX has a more user readable email notification possiblities. So you can attach the complete job output to your notifications.

E.g. edit the notification templates as following is now possible:

{{ job_friendly_name }} #{{ job.id }} had status {{ job.status }}, view details at {{ url }}

{{ job_metadata.stdout }}

In this fork you can access the job_metadata field as json object and not as string as in upstream project. The following fields are made accessible:

 'job_metadata': {'url': 'https://towerhost/$/jobs/playbook/13',
                                    'traceback': '',
                                    'status': 'running',
                                    'started': '2019-08-07T21:46:38.362630+00:00',
                                    'project': 'Stub project',
                                    'playbook': 'ping.yml',
                                    'name': 'Stub Job Template',
                                    'limit': '',
                                    'inventory': 'Stub Inventory',
                                    'id': 42,
                                    'hosts': {},
                                    'friendly_name': 'Job',
                                    'finished': False,
                                    'credential': 'Stub credential',
                                    'created_by': 'admin',
                                    'stdout': 'Job output'}

The stdout field is additionally made accesible.

To change your Notification templates go to Administration > Notifications > Edit > check Customize messages. A complete guide can be found in official documentation at https://docs.ansible.com/ansible-tower/latest/html/userguide/notifications.html#create-custom-notifications .

The following information are related to the official AWX project:

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is the upstream project for Tower, a commercial derivative of AWX.

To install AWX, please view the Install guide.

To learn more about using AWX, and Tower, view the Tower docs site.

The AWX Project Frequently Asked Questions can be found here.

The AWX logos and branding assets are covered by our trademark guidelines.

Contributing

• Refer to the Contributing guide to get started developing, testing, and building AWX.
• All code submissions are made through pull requests against the devel branch.
• All contributors must use git commit --signoff for any commit to be merged and agree that usage of --signoff constitutes agreement with the terms of DCO 1.1
• Take care to make sure no merge commits are in the submission, and use git rebase vs. git merge for this reason.
• If submitting a large code change, it's a good idea to join the #ansible-awx channel on irc.freenode.net and talk about what you would like to do or add first. This not only helps everyone know what's going on, but it also helps save time and effort if the community decides some changes are needed.

Reporting Issues

If you're experiencing a problem that you feel is a bug in AWX or have ideas for improving AWX, we encourage you to open an issue and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.

Code of Conduct

We ask all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions or need assistance, please reach out to our community team at [email protected]

Get Involved

We welcome your feedback and ideas. Here's how to reach us with feedback and questions:

• Join the #ansible-awx channel on irc.freenode.net
• Join the mailing list

License

Apache v2