You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that AWX is open source software provided for free and that I might not receive a timely response.
Feature type
Enhancement to Existing Feature
Feature Summary
Hi team,
I have an idea for survey in AWX. Apart dynamic form, i notice that we can assign to Question a variable like key.sub_key and during launch of job this variable is correctly papped in yaml like:
key:
sub_key: 1
But, if we not have "prompt on launch" in extra_vars, this type of variable is ignored and not passed to job.
If we set "prompt on launch" in extra_vars, the variable is passed to job two times, one in dot version and one in yml version, like:
key.sub_key: 1key:
sub_key: 1
Probably is not a "standard" use case, or os better map object in playbook itself, but this can be usefull in certain use case.
Select the relevant components
UI
API
Docs
Collection
CLI
Other
Steps to reproduce
Create a survey with variable with dot
Current results
If we set "prompt on launch" in extra_vars, the variable is passed to job two times, one in dot versione and one in yml version, like:
if we not have "prompt on launch" in extra_vars, this type of variable is ignored and not passed to job.
Sugested feature result
dot variable passed as a object, and not ignored if extra_vars is not prompted.
If extra_vars is prompted, ignore dot version and use object
Additional information
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following
Feature type
Enhancement to Existing Feature
Feature Summary
Hi team,
I have an idea for survey in AWX. Apart dynamic form, i notice that we can assign to Question a variable like
key.sub_key
and during launch of job this variable is correctly papped in yaml like:But, if we not have "prompt on launch" in extra_vars, this type of variable is ignored and not passed to job.
If we set "prompt on launch" in extra_vars, the variable is passed to job two times, one in dot version and one in yml version, like:
Probably is not a "standard" use case, or os better map object in playbook itself, but this can be usefull in certain use case.
Select the relevant components
Steps to reproduce
Create a survey with variable with dot
Current results
If we set "prompt on launch" in extra_vars, the variable is passed to job two times, one in dot versione and one in yml version, like:
if we not have "prompt on launch" in extra_vars, this type of variable is ignored and not passed to job.
Sugested feature result
dot variable passed as a object, and not ignored if extra_vars is not prompted.
If extra_vars is prompted, ignore dot version and use object
Additional information
No response
The text was updated successfully, but these errors were encountered: