Replies: 3 comments 5 replies
-
Nice idea... how about a twist as follows? actions:
- finish:
- task: common/tekton-trigger-message # creates a slack message and populates the context with this message
with:
msgId: my-tekton-msg
- task: common/github-message # creates a Tekton message and populates the context with this message
with:
msgId: my-gh-msg
- task: common/webhook
with:
URL: http://
user: username
secret: default/secret
type: [GET|POST]
body: my-tekton-msg # creates a GH message and populates the context with this message
- task: common/webhook
with:
URL: http://
user: username
secret: default/secret
type: [GET|POST]
body: my-gh-msg |
Beta Was this translation helpful? Give feedback.
4 replies
-
This could be used as a basis the |
Beta Was this translation helpful? Give feedback.
0 replies
-
I believe that we will want to support placeholders in URL, headers and the body as we do for metrics. Values could come from the referenced secret or from the experiment. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Purpose:
I want to discuss if there's a way to define a generic webhook interface, e.g.,
so that we can re-use the same interface to implement
gitops/github_action
andnotification/slack
.Github Action APIs are defined here: https://docs.github.com/en/rest/reference/actions#create-a-workflow-dispatch-event
@kalantar @sriumcp @fabolive ^^
Beta Was this translation helpful? Give feedback.
All reactions