John Westcott thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API.
It may be a good idea to add that information into the "help ()" field in the plugin's job box.
[~johnwestcottiv] thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API.
It may be a good idea to add that information into the "help ((?))" field in the plugin's job box.
John Westcott thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API.
It may be a good idea to add that information into the "help ( )" field in the plugin's job box.
Thanks for the follow up. I'll add a task for indicating that in the help entries. In addition, there should be a message in the jenkins job logs like:
[WARNING]: Extra variables defined but prompt for variables on launch is not set in tower job