Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add webhookUrl field into GitServer form #242

Closed
callmevladik opened this issue May 16, 2024 · 1 comment
Closed

Add webhookUrl field into GitServer form #242

callmevladik opened this issue May 16, 2024 · 1 comment
Assignees
Labels
feature New functionality

Comments

@callmevladik
Copy link
Contributor

callmevladik commented May 16, 2024

In the Configuration Section of the Portal (under Configuration, GitServer), we need to implement a field for the Webhook URL that can be defined by the user. This enhancement should also include a comprehensive description clarifying that this field is optional. Our system will attempt to retrieve the webhook URL automatically via our codebase operator from the Ingress object. However, in scenarios where Ingress is not available, this field will enable users to manually specify their webhook URL. Additionally, we need to implement logic in the UI similar to that in the codebase-operator to potentially show users what the webhook URL is, even if it's auto-detected.

Acceptance Criteria:

  1. A new Webhook URL field is implemented in the GitServer configuration section of the Portal.
  2. The field includes a detailed description that explains its optional nature and its operational mechanism.
  3. Logic is implemented in the UI to automatically obtain the webhook URL from the Ingress object, mirroring the functionality present in the codebase-operator.
  4. The UI should be capable of displaying the detected webhook URL to the user, enhancing transparency and usability.
  5. In the absence of an Ingress object, the system allows users to manually enter a Webhook URL.

https://github.com/epam/edp-tekton/blob/master/charts/pipelines-library/templates/resources/gitservers/gitserver.yaml#L18

@callmevladik callmevladik converted this from a draft issue May 16, 2024
@callmevladik callmevladik self-assigned this May 16, 2024
@callmevladik callmevladik added the feature New functionality label May 16, 2024
SergK pushed a commit that referenced this issue May 16, 2024
@callmevladik callmevladik moved this from In Progress to In Review in KubeRocketCI (EPAM Delivery Platform) May 17, 2024
@callmevladik callmevladik moved this from In Review to In QA in KubeRocketCI (EPAM Delivery Platform) May 17, 2024
@Serg1506
Copy link

Screenshot_62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality
Projects
Development

No branches or pull requests

2 participants