You can currently only set ask_variables_on_launch via an API. However, once you submit via the UI, it removes that.
ask_variables_on_launch and set to trueask_variables_on_launch and see it is trueask_variables_on_launch and see it is false
UI to have no impact on anything else
UI resests ask_variables_on_launch
You're running a fairly old version of AWX and I'm unable to reproduce on the latest version. Reopen if found against 2.X+
@matburt how do I reopen?
It was found using same steps in < AWX 2.0.1 >, though I guess I said submit, where I should have said save. Should be reproducible on your side with little effort, if not, please let me know what you are seeing.
It's a bit blury on the gif, but I think you can still make out that it went from true to false.
https://gph.is/2AuTI5a
From the GIF, you are patching in the API while the UI edit page is open. The UI will not track API updates that happen after you open the edit page; this is not something we have a mechanism to fix at this point.
@wenottingham I don’t think that is the issue, that was just the demonstration, can you leave this open until it is confirmed?
Confirmed, if you rewatch the GIF, there is no patching being done, I simply show that it is true (via the UI), and then returns to false (via the UI). Can you @matburt or @wenottingham can you please reopen the issue?
UI will now use a PATCH instead of a PUT when updating a workflow job template. Corresponding commit is here
Most helpful comment
UI will now use a PATCH instead of a PUT when updating a workflow job template. Corresponding commit is here