diff options
| author | Aaron Tan <jangsutsr@gmail.com> | 2016-11-21 16:31:52 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-11-21 16:31:52 +0100 |
| commit | 220f44bdbce077ef581ca6e49a5fc1495154968e (patch) | |
| tree | 7742856bcbc58ec0374ee76a843d221a03e6992d /docs | |
| parent | Remove 'ancestor_artifacts' (diff) | |
| download | awx-220f44bdbce077ef581ca6e49a5fc1495154968e.tar.xz awx-220f44bdbce077ef581ca6e49a5fc1495154968e.zip | |
Give updated copy name format
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/workflow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/workflow.md b/docs/workflow.md index 5a7d9d250b..1f9ee7a3f6 100644 --- a/docs/workflow.md +++ b/docs/workflow.md @@ -49,7 +49,7 @@ Workflow job summary: ### Workflow Copy and Relaunch Other than the normal way of creating workflow job templates, it is also possible to copy existing workflow job templates. The resulting new workflow job template will be identical to which it copies from, except for `name` field which will be appended a text to indicate it's a copy. -Workflow job templates can be copied by POSTing to endpoint `/workflow_job_templates/\d+/copy/`. After copy finished, the resulting new workflow job template will have identical fields including description, extra_vars, labels, 'launch_type' and survey-related fields (survey_passwords, survey_spec and survey_enabled). More importantly, all workflow job template nodes of the original workflow job template, as well as the topology they bear, will be copied. On the other hand, schedules and notification templates of the original workflow job template will not be copied nor shared, and the name of the created workflow job template is the original name plus a special-formatted suffix to indicate its copy origin, such as **TODO**. +Workflow job templates can be copied by POSTing to endpoint `/workflow_job_templates/\d+/copy/`. After copy finished, the resulting new workflow job template will have identical fields including description, extra_vars, labels, 'launch_type' and survey-related fields (survey_passwords, survey_spec and survey_enabled). More importantly, all workflow job template nodes of the original workflow job template, as well as the topology they bear, will be copied. On the other hand, schedules and notification templates of the original workflow job template will not be copied nor shared, and the name of the created workflow job template is the original name plus a special-formatted suffix to indicate its copy origin as well as the copy time, such as 'copy_from_name@10:30:00 am'. Worflow jobs cannot be copied directly, instead a workflow job is implicitly copied when it needs to relaunch. Relaunching an existing workflow job is done by POSTing to endpoint `/workflow_jobs/\d+/relaunch/`. What happens next is the original workflow job is copied to create a new workflow job. The new workflow job then gets a copy of all nodes of the original as well as the topology they bear. Finally the full-fledged new workflow job is triggered to run, thus fulfilling the purpose of relaunch. |