This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Webhook configuration in Keptn Bridge #6748
johannes-b
started this conversation in
Ideas
Replies: 1 comment
-
@Kirdock already had the same idea of combining the webhook config and secret creation: #6299 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In a nutshell, I would like to discuss these aspects when configuring a Webhook using Bridge:
Modify bridge entry point to select a project and provide a pre-filled form
User Journey: I'm on the ArtifactHub and found an integration I would like to activate by its Webhook for my Keptn instance. The integration on the ArtifactHub (e.g., Slack) provides details about the Webhook (e.g., URL, custom payload, custom headers) and can provide these details. These details are then used to pre-fill the Webhook configuration form. Consequently, I'm very close to saving and activating it; most likely a secret is needed.
Step 1: Integration on ArtifactHub:
Step 2: Forward to Keptn, where the user has to select the project first:
Step 3: Information provided by the integration is already pre-filled:
Combine secret and webhook creation
Status quo: When creating a webhook configuration for integrating a DevOps tool using its webhook, I start configuration but then realize that secrets are missing that need to be created first.
Allow creation of Webhook without available task
It can be the case, that I want to integrate tooling for which no
task
is in the Shipyard yet. However, this should not stop the process. Consequently, I would like to add a subscription on a custom task, which will not be active until the task is added to the sequence in Shipyard.These are UX improvements for configuring Webhooks. Feedback is welcome!
Beta Was this translation helpful? Give feedback.
All reactions