-
Notifications
You must be signed in to change notification settings - Fork 898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate with external Tower Workflow #17441
Comments
I would leave the "job_template" bit out of the schema naming. We shouldn't use provider specific terminology in an agnostic modeling. I also don't really understand there being two "trees" of data (workflows and workflow nodes). Can you give a more complex example, and how it would fit into your model? |
Additionally, why do we even need all of this information. The request is to just launch a workflow. I would think we'd only need the workflows themselves and not their component parts.
Can you elaborate a bit? Can the surveys just be part of the workflow defintion inventory? |
@Fryguy I've updated the issue description. (The Inventorying the individual |
Talked to @Fryguy and we don't need the level of detail into |
@jameswnl is this still an open issue? If not, can you close it. |
Yep, we can close this. |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1468339
Using this issue to track all related work
Backend
To inventory Tower
Workflow
objects to allow user launching them from within MIQ.A Workflow in Tower
The following figure shows a Tower
workflow_job_template
Native Tower models
Demo Job Template
,billy
etc.) are theworkflow_job_template_nodes
of the containingworkflow_job_template
workflow_job_template_nodes
points to ajob_template
(Demo Job Template
etc)job_template
and they are eithersuccess|failure|always
When this
workflow_job_template
is started, it will launchjob_template
named asDemo Job Template
and thenbilly
and then finally depending on outcome ofbilly
, launchhello_template_with_survey
on success orhello_template
on failure.Tower API output of a `workflow_job_template`
Tower API output of its `workflow_job_template_nodes`
MIQ models and their Tower native counterparts
workflow
=> (Tower native)workflow_job_template
PRs:
#17440
ManageIQ/manageiq-providers-ansible_tower#86
ansible/ansible_tower_client_ruby#104The above PRs achieve the following:
workflow
would have the following attributes collected:name
survey_spec
variables
a_workflow.run(params_json)
.Frontend
@h-kataria
Automate (?)
@gmcculloug ?
The text was updated successfully, but these errors were encountered: