8049-expose execution node var for playbook

[lucas-benedito]

SUMMARY

Feature Overview
Expose the Execution Node name as a variable for playbooks(awx_execution_node).

Background, and strategic fit
Customers running jobs in Ansible Tower use the ansible_hostname as an identifier for external applications requests (i.e.: Splunk, Service Now, etc ). In the Ansible Automation platform, that value is the container hostname which is now known to the customer and is not useful.

(Optional) Use Cases

• delegate the job to the specific cluster node
• define an identifier for external services such as Splunk, Service Now, etc.

ISSUE TYPE

• New or Enhanced Feature

COMPONENT NAME

• CLI

AWX VERSION

2.3

[TheRealHaoLiu]

just out of curiosity what is 8049 in reference to?

[TheRealHaoLiu]

is this a reference to a JIRA issue? if so are you able to see the Automation Controller Project? please edit Jira issue field in the project

[lucas-benedito]

@TheRealHaoLiu yes, that is the Jira issue, i will update the field accordingly. Thanks for the feedback

[ffirg]

This one might be better served once constructed inventory has landed and we can then make better use of hostvars etc

[fosterseth]

we may wish to update our functional test to assert the execution node is passed in

awx/awx/main/tests/unit/models/test_unified_job_unit.py

Line 96 in 23a34c5

def test_job_metavars(self):

Can you update the PR for that?

[fosterseth]

comfirmed that execution node is injected into the extra vars, here is the extravars file in the private data dir

bash-5.1$ tail -n 1 extravars 
!unsafe 'tower_execution_node': !unsafe 'awx_1'