Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-2348

NameSpace specified in EventListener route URL as a parameter

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Tekton Triggers
    • NameSpace specified in EventListener route URL as a parameter
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      The customer wants to use the feature Configuring event listeners to serve multiple namespaces. To enhance the feature they want the below parameter to filter out the event listener.  

      The customer is having ~1400 namespaces &  counting which are difficult to mention in the EventListner resource.

       

      {{}}

      {{Namespace specified in EventListener route url as a parameter
      json_request=\$(cat <<EOF
      {
      "branch": "${params.branch}",
      "wasDeploy": "${params.wasDeploy}",
      "deployFeatureArtifacts": "${params.deployFeatureArtifacts}",
      "email": "\$build_user_mail",
      "pipelinerun_id": "${pipelinerun_id}"
      }
      json_response=\$(curl -ksb --header "Content-Type: application/json" --request POST --data "\$json_request" https://deploy-bsa-gitops.apps.ocptest3.akbank.com?namespace=bsa-devops-prep)}}

              rh-ee-kbaig Khurram Baig
              rhn-support-vsolanki Vimal Solanki
              Archiver:
              rh-ee-ntatinen Navya Tatineni

                Created:
                Updated:
                Archived: