Merge pull request #49 from jduimovich/add-gitlab-auth

auth-secret in template for gitlab and github

skeleton/backstage/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: sed.edit.CATALOG_DESCRIPTION 
           dockerfile: sed.edit.DOCKERFILE
           buildContext: sed.edit.BUILDCONTEXT
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: 'sed.edit.APPTAGS'
           owner: ${{ parameters.owner }} 

skeleton/gitops-template/.tekton/README.md

@@ -6,15 +6,15 @@ This pipeline is used to validate pull-requests into the gitops repository. This
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 
 ## Templates 

skeleton/source-repo/.tekton/README.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

skeleton/source-repo/.tekton/docker-pull-request.yaml

@@ -38,6 +38,8 @@ spec:
       value: '{{revision}}'
     - name: event-type
       value: '{{event_type}}'
+    - name: gitops-auth-secret-name
+      value: ${{ values.gitopsSecretName }}
   pipelineRef:
     name: docker-build-rhtap
   workspaces:

skeleton/source-repo/.tekton/docker-push.yaml

@@ -38,6 +38,8 @@ spec:
       value: '{{revision}}'
     - name: event-type
       value: '{{event_type}}'
+    - name: gitops-auth-secret-name
+      value: ${{ values.gitopsSecretName }}
   pipelineRef:
     name: docker-build-rhtap
   workspaces:

templates/devfile-sample-code-with-quarkus-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-code-with-quarkus-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for Quarkus Java example with advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures,  attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment 
           dockerfile: src/main/docker/Dockerfile.jvm.staged
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["java", "quarkus", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }} 

templates/devfile-sample-dotnet60-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-dotnet60-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for C# .Net 6.0 example with advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures,  attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment 
           dockerfile: docker/Dockerfile
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["net", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }} 

templates/devfile-sample-go-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-go-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for Go Runtime http based application with advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures,  attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment 
           dockerfile: docker/Dockerfile
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["go", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }} 

templates/devfile-sample-java-springboot-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-java-springboot-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for Spring Boot® using Maven sample HTTP/REST application based application with advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures,  attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment 
           dockerfile: docker/Dockerfile
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["java", "spring", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }} 

templates/devfile-sample-nodejs-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-nodejs-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for Node.js+Express REST API with advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures,  attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment 
           dockerfile: Dockerfile
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["nodejs", "express", "ubi8", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }} 

templates/devfile-sample-python-dance/content/docs/pipelines.md

@@ -1,20 +1,20 @@
 # docker-build-rhtap
 
-## Shared Git resolver model for shared pipeline and tasks. 
+## Shared Git resolver model for shared pipeline and tasks
 
 This pipeline is used to create dockerfile based sscs builds. The pipeline run by this runner will clone the source, build an image with SBOM, and attestations and push these to the users image registry.  
 
 Tasks references come from this repository ` ../pipelines` `../tasks` and are referenced by URL using the git resolver in tekton. 
 
-When the pipleines in this repo are updated, all future runs in existin pipelines are shared.
+When the pipleines in this repo are updated, all future runs in existing pipelines are shared.
 
 A developer can override these tasks with a local copy and updated annotations. 
 
 Example 
 
 To override the git-clone task, you may simply copy the git reference into your .tekton directory and then reference it from the remote task annotation. 
 
-`pipelinesascode.tekton.dev/task-0: "./tekton/git-clone.yaml"` 
+`pipelinesascode.tekton.dev/task-0: ".tekton/git-clone.yaml"` 
 
 ## Templates 
 These pipelines are in template format. The references to this repository in the PaC template is `{{values.rawUrl}}` which is updated to point to this repo or the fork of this repo.

templates/devfile-sample-python-dance/template.yaml

@@ -141,6 +141,7 @@ spec:
           description: Secure Supply Chain Example for Python is an interpreted,  object-oriented, high-level programming language with dynamic semantics. This sample demonstrates software supply chain security functionalty using an advanced continuous integration pipeline covering building, CVE scanning, security scanning, signatures, attestations, SLSA provenance and SBOM along with Gitops-based continuous deployment. 
           dockerfile: docker/Dockerfile
           buildContext: .
+          gitopsSecretName: ${{ 'gitops-auth-secret' if parameters.hostType === 'GitHub' else 'gitlab-auth-secret' }}
           image: '${{ parameters.imageRegistry }}/${{ parameters.imageOrg }}/${{ parameters.imageName }}'
           tags: '["python", "pip", "flask", "sscs", "sbom", "acs"]'
           owner: ${{ parameters.owner }}