ansible / ansible/awx

Print inventory host details and play recap on notification mail

Open
#13,232 3 comments 0 reactions 0 assignees View on GitHub
community type:enhancement
Dominant language
Python
Stars
15.6k
Forks
3.7k
Avg merge
2d 15h
Merged PRs (30d)
25

Description

### Please confirm the following

- [X] I agree to follow this project's [code of conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
- [X] I have checked the [current issues](https://github.com/ansible/awx/issues) for duplicates.
- [X] I understand that AWX is open source software provided for free and that I might not receive a timely response.

### Feature type

New Feature

### Feature Summary

Print inventory's host details on mail notification.

Print PLAY RECAP of job on mail notification.

### Select the relevant components

- [ ] UI
- [ ] API
- [ ] Docs
- [ ] Collection
- [ ] CLI
- [X] Other

### Steps to reproduce

trigger a job

### Current results

Job #419134 had status successful, view details at https://awx/#/jobs/playbook/419134

Patching completed successfully on 19 servers.

### Sugested feature result

Job #419134 had status successful, view details at https://awx/#/jobs/playbook/419134

Patching completed successfully on 19 servers.

inventory host details,
host1
host2
host3
...
host19

PLAY RECAP *********************************************************************
host1 : ok=57 changed=17 unreachable=0 failed=0 skipped=32 rescued=1 ignored=0
host2 : ok=57 changed=17 unreachable=0 failed=0 skipped=32 rescued=1 ignored=0
host3 : ok=57 changed=17 unreachable=0 failed=0 skipped=32 rescued=1 ignored=0
....
host19 : ok=57 changed=17 unreachable=0 failed=0 skipped=32 rescued=1 ignored=0

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing AWX's job notification mail flow from a triggered job. Determine where inventory host details and the PLAY RECAP are available, then verify that successful job emails include both sections for all hosts. No files or tests are identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.