Set Default Values for Survey Variables in Scheduled Tasks

[lmrlyv]

I use Survey Variables in the Task Template to set values for the variables defined in the vars_prompt section of the playbook. This works fine when I manually trigger the task and enter the values by hand. However, I haven't found a way to set these variables when the task template is scheduled to run automatically. Is there currently a way to achieve this? If not, wouldn't it be better to allow defining default values when creating a schedule?

[lmrlyv]

Hi, @fiftin, @matejkramny, and @strangeman. Sorry to push for a response, but I'd really appreciate your thoughts on this question/idea. What do you think?

[northwestnodes-eric]

A bit of a late reply, but no one here seems interested in really helping each other. You can set default variables for the playbook itself like so: hosts: "{{ target_hosts | default('servers') }}" where you can set a target_hosts survey variable as needed and leave it empty to default to 'servers'. Might not work for your situation, but I see no other option at the moment.

[lmrlyv]

Thank you for the reply though.

Yeah, it feels like the project is abandoned or has very little development going on.

I don’t remember exactly but if I am not mistaken, the playbook execution gets stuck on the user input indefinitely when it is triggered on schedule even though the default value for vars_prompt is defined in the playbook itself.

I will try this out again tomorrow and update here the exact behavior

[jengstrom440]

Hello, wondering if you had any success? I am looking at several different scenarios and I really wish the surveys worked like Ansible Automation Platform 2.4 or AWX 18+. I would also like to create a default value for a survey question, but should I wish upon launch, change it to something else; otherwise use the answer I provided. I don't want to put it in the playbook though because I need several different playbooks then!

[mg-oerp]

I'm running into similar issues but with trying to figure out how to pass static variables to a schedule. I don't want to end up having to duplicate the same playbook with hard coded bits a hundred times just because I want to schedule them...

Thank you for the reply though.

Yeah, it feels like the project is abandoned or has very little development going on.

I don’t remember exactly but if I am not mistaken, the playbook execution gets stuck on the user input indefinitely when it is triggered on schedule even though the default value for vars_prompt is defined in the playbook itself.

I will try this out again tomorrow and update here the exact behavior

I'm starting to think the same thing. It seems like things have been added semi-recently, but there also seems to be some large gaps in what it can and can't do and it doesn't seem like it's got much momentum anymore. Thinking maybe this is not the solution I was hoping it might become.