Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-322

[EAP7-1337] Allow users to setup a source clone secrets manually

XMLWordPrintable

    • Icon: Quality Risk Quality Risk
    • Resolution: Unresolved
    • Icon: Major Major
    • OpenShift
    • None

      Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add sourceSecret field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-inputs.html#builds-adding-source-clone-secrets_creating-build-inputs for more details on the source secret functionality.

      Users could use the source-secret-match-uri method to link sourceSecret automatically, but I think we should allow them to use sourceSecret as well to provide support both options how to solve this.

              jmesnil1@redhat.com Jeff Mesnil
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: