Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-5623

Passing arbitary values to incoming webhook

XMLWordPrintable

    • 3
    • Documentation (Ref Guide, User Guide, etc.), User Experience
    • Hide
      Let users pass parameters to the incoming webhook.

      We accept now JSON payloads in the incoming webhook and we can pass the params to the pipelinerun dynamically.

      Allowed params to be passed need to be explicitly defined in the Repository CR to avoid for an extra security layer.
      Show
      Let users pass parameters to the incoming webhook. We accept now JSON payloads in the incoming webhook and we can pass the params to the pipelinerun dynamically. Allowed params to be passed need to be explicitly defined in the Repository CR to avoid for an extra security layer.
    • ---
    • ---

      Story (Required)

      As a User I would like to define the parameters passed in incoming webhook

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      https://hackmd.io/10Oj3bnZTYWKOHVQeil07A

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              mramendi Mikhail Ramendik
              mramendi Mikhail Ramendik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: