forked from harness-community/idp-samples
-
Notifications
You must be signed in to change notification settings - Fork 0
/
workflows-ca-inputset.yaml
52 lines (52 loc) · 1.59 KB
/
workflows-ca-inputset.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
name: test-custom-action
title: Test New Custom Actions
description: New custom action to trigger harness pipeline using inputset
tags:
- inputset
spec:
owner: debabrata.panigrahi
type: service
parameters:
- title: Service Details
required:
- inputSetName
- triggerName
properties:
inputSetName:
title: Name your Input Set
type: string
description: Unique Name for Inputset
triggerName:
title: Name for Trigger
type: string
description: Name for Trigger
owner:
title: Owner
type: string
description: Owner of the component
ui:field: OwnerPicker
ui:options:
catalogFilter:
kind: Group
token:
title: Harness Token
type: string
ui:widget: password
ui:field: HarnessAuthToken
steps:
- id: trigger
name: Creating your react app
action: trigger:trigger-pipeline-with-webhook
input:
url: "https://qa.harness.io/ng/account/zEaak-FLS425IEO7OLzMUg/idp-admin/orgs/default/projects/idptestproject/pipelines/idpnewcustomaction/pipeline-studio/?storeType=INLINE"
inputSetName: ${{ parameters.inputSetName }}
triggerName: ${{ parameters.triggerName }}
apikey: ${{ parameters.token }}
# The final step is to register our new component in the catalog.
output:
links:
- title: Pipeline Details
url: ${{ steps.trigger.output.PipelineUrl }}