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
Copy file name to clipboardExpand all lines: _docs/gitops-quick-start/quick-start-promotion-workflow.md
+111-7Lines changed: 111 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,19 +20,123 @@ In this quick start guide, we'll see how to create an Argo WorkflowTemplate usin
20
20
21
21
##Example 1: Slack notification
22
22
23
-
Creating a Promotion Workflow is as simple as creating an[Argo WorkflowTewmplate[(https://argo-workflows.readthedocs.io/en/latest/workflow-templates/).
23
+
Creating a Promotion Workflow is as simple as creating an[Argo WorkflowTewmplate[(https://argo-workflows.readthedocs.io/en/latest/workflow-templates/).
24
24
You can do so directly from the UI.
25
25
26
26
#####Step-by-step
27
27
28
-
1. In the Codefresh UI, from the sidebar, select**Promotion Workflows**, and click**Add Promotion Workflow**.
28
+
1. In the Codefresh UI, from the sidebar, select**Promotion Workflows**, and
29
+
click**Add Promotion Workflow**.
29
30
1. Define the following:
30
-
1.**Name**: A unique name for the Promotion Workflow,`slack-notification` for the quick start.
31
-
1.**Description**: A meaningful comment on what the workflowTemplate is doing,`A template to send a Slack notification when a promotion start` in our case.
32
-
1.**Resource Filename**: the name of the manifest file that will be saved under the`resources/control-planes/promotion-workflows`
33
-
folder in your Shared Configuration Repository. LEave as-is for the quick-start.
31
+
1.**Name**: A unique name for the Promotion Workflow,`slack-notification`
32
+
for the quick start.
33
+
1.**Description**: A meaningful comment on what the workflowTemplate is
34
+
doing,`A template to send a Slack notification when a promotion start` in
35
+
our case.
36
+
1.**Resource Filename**: the name of the manifest file that will be saved
37
+
under the`resources/control-planes/promotion-workflows`
38
+
folder in your Shared Configuration Repository. Leave as-is for the