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

Pipeline as code: validate repository url uniqueness

    XMLWordPrintable

Details

    • Pipeline as code: validate repository url uniqueness
    • False
    • False
    • To Do
    • 0
    • 0% 0%
    • Hide
      * With this update, as a developer, the `tkn-pac` CLI tool notifies you if you create a duplicate repository to a {pac} runs. When you use`tkn pac repo create`, each repository must have a unique URL. This notification also helps prevent hijacking executions.
      Show
      * With this update, as a developer, the `tkn-pac` CLI tool notifies you if you create a duplicate repository to a {pac} runs. When you use`tkn pac repo create`, each repository must have a unique URL. This notification also helps prevent hijacking executions.

    Description

      Goal

      As a developer, I need assistance to prevent adding a single repository multiple times for pipeline as code executions and prevent hijacking executions.

      Acceptance Criteria

      • When developer adds a new repository using "tkn pac create repo", they should be informed about an existing repository with the same url, should a repo with that url already exist.

      Questions

      • Should user be prevented to create a new repo with a Git repo that already exists on the cluster? Can we support multiple namespaces for a single repo?

      Attachments

        Activity

          People

            smukhade Shivam Mukhade (Inactive)
            ssadeghi@redhat.com Siamak Sadeghianfar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: