Open Sispheor opened 3 years ago
Any change on this issue ?
Not yet scheduled. But still in our TODO.
name: AAP API hosts: localhost gather_facts: false
vars: aap_user: USER aap_pass: PASS aap_host: aapcontrol001.lnx.example.local template_nun: 21
tasks:
name: Get the token AAP uri: url: "https://{{ aap_host }}/api/v2/users/1/personal_tokens/" method: POST validate_certs: false return_content: true user: "{{ aap_user }}" password: "{{ aap_pass }}" force_basic_auth: true status_code: 201 register: response
name: Use the token uri: url: "https://{{ aap_host }}/api/v2/workflow_job_templates/{{ template_nun | urlencode }}/launch/" method: POST validate_certs: false return_content: true status_code: 201 headers: Authorization: "Bearer {{ response['json']['token'] }}" Content-Type: "application/json" register: launch
Too complex add workflow in squesh?
Not a priority on our side. We are working on a V2 that refactor a lot of thing.
Is v2 development public? We can help?
Here we need a user story. What do we want to manage at Squest level? The first survey, like we already do with job templates. And then what about approval nodes? We leave them to Tower/AWX? We catch them and expose into Squest? As Squest already manage its own approval workflow system, it would a feature duplicate.
Note that it's already possible to create a job template that will trigger a workflow if the idea is to execute multiple job template at once.
So far Squest only support job templates. It would be interesting to support as well workflows.