[jboss-jira] [JBoss JIRA] (WFWIP-322) [EAP7-1337] Allow users to setup a source clone secrets manually

[Petr Kremensky (Jira)]

     [ https://issues.redhat.com/browse/WFWIP-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petr Kremensky updated WFWIP-322:
---------------------------------
    Description: 
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.

  was:
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 a full support for this.



> [EAP7-1337] Allow users to setup a source clone secrets manually
> ----------------------------------------------------------------
>
>                 Key: WFWIP-322
>                 URL: https://issues.redhat.com/browse/WFWIP-322
>             Project: WildFly WIP
>          Issue Type: Quality Risk
>          Components: OpenShift
>            Reporter: Petr Kremensky
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)