Merge pull request #184 from stakater/restructure-pipeline

Restructure pipeline

content/for-developers/tutorials/outer-loop/add-ci-pipeline/01-overview.md

@@ -6,18 +6,19 @@ To be able to run a pipeline using Tekton pipeline-as-code. The delivery enginee
 
 **For the Delivery Engineer:**
 
-1. Manage Application Secrets
-   - For each application, securely deploy the required secrets within the respective namespace housing the pipeline-as-code setup.
+1. Bootstrap `infra-gitops-config` repository
+1. Deploy Organization level secret
+1. Bootstrap `apps-gitops-config` repository
 
 **For the Developer:**
 
+1. Create Webhook
+   - Configure the Webhook for the Pipeline.
+1. Create Repository Secret
+   - Pipeline as code needs a secret to securely communicate with the Application Repository. This secret is deployed by the developer through the `apps-gitops-config` repository.
 1. Define Repository Resource
    - Set up the Repository resource within the tenant's designated build namespace. This resource will link to the application's source code repository.
-1. Configure Repository Access
-   - Securely deploy a secret within the build namespace. This secret will provide the necessary credentials to access the application's Git repository.
 1. Create PipelineRun
    - Author a PipelineRun that encapsulates the specific workflow for the application. This defines how the source code will be built, tested, and deployed.
-1. Deploy Required Secrets
-   - If any additional secrets are required during the pipeline run, ensure they are securely deployed within the appropriate namespace.
 
 By following these steps, the delivery engineer and the developer can collaboratively set up and execute Tekton pipelines as code efficiently and securely.

content/for-developers/tutorials/outer-loop/prerequisites.md

@@ -6,8 +6,6 @@ Before you embark on setting up your pipeline as code, it's essential to ensure
 
 In certain cases, you may need to add a new environment to an existing application within a tenant. For example, when incorporating a production cluster into your infrastructure, you'll want to extend your application's deployment capabilities to this new environment. Ensure you have a clear understanding of how to add and configure this environment to your application as part of your prerequisites.
 
-## [Personal Access Token (PAT)](./add-ci-pipeline/04.1-configure-github-access.md)
-
 A Personal Access Token (PAT) is an essential component for ensuring secure and authenticated interactions with your code repositories. This token serves as a vital bridge between your pipeline and your version control system, allowing it to access and manage your code repositories. Whether it's for fetching code, creating branches, or managing pull requests, this token is the cornerstone of performing Git operations securely.
 
 ## [SSH Keys for Repository Access](./github-ssh/github-ssh.md)

mkdocs.yml

@@ -150,11 +150,8 @@ nav:
                 - Configure Pipeline for your application:
                   - for-developers/tutorials/outer-loop/add-ci-pipeline/01-overview.md
                   - for-developers/tutorials/outer-loop/add-ci-pipeline/03-create-webhook.md
-                  - Add Repository:
-                    - for-developers/tutorials/outer-loop/add-ci-pipeline/04.0-add-repository-overview.md
-                    - for-developers/tutorials/outer-loop/add-ci-pipeline/04.1-configure-github-access.md
-                    - for-developers/tutorials/outer-loop/add-ci-pipeline/04.2-add-external-secret.md
-                    - for-developers/tutorials/outer-loop/add-ci-pipeline/04.3-create-repository.md
+                  - for-developers/tutorials/outer-loop/add-ci-pipeline/04-add-repository-secret.md
+                  - for-developers/tutorials/outer-loop/add-ci-pipeline/05-create-repository.md
                   - for-developers/tutorials/outer-loop/add-ci-pipeline/06-adding-pipeline.md
                 - for-developers/tutorials/outer-loop/promote-application/promote-app.md
         - How-to guides: