break advanced configure into 3 separate pages

content/en/plugins/github-integration/authz.md

@@ -0,0 +1,99 @@
+---
+title: Enable and Configure AuthZ in the GitHub Integration Plugin
+linkTitle: Enable AuthZ
+weight: 10
+description: >
+  Learn how to enable and configure AuthZ support for GitHub App accounts.
+---
+
+
+![Proprietary](/images/proprietary.svg) ![Beta](/images/beta.svg)
+
+## Authorization (AuthZ)
+
+This feature enables AuthZ support for GitHub App accounts.
+
+Fiat is the Spinnaker microservice responsible for authorization (authz) for the other Spinnaker services. It is not enabled by default, so users are able to perform any action in Spinnaker. When enabled, Fiat checks the user's permissions before allowing the action to proceed.
+
+### How this feature works
+
+The GitHub Integration plugin supports Fiat authz for GitHub App accounts configured to determine whether a role or group can perform the following actions:
+
+- `READ`: A user can view the GitHub App account's configuration and/or use it as a trigger source.
+- `WRITE`: A user can use the GitHub App account as the target account for the GitHub integration plugin stages.
+
+
+```mermaid
+sequenceDiagram
+	participant user as User
+	participant gate as Gate
+	participant orca as Orca
+	participant igor as Igor
+	participant fiat as Fiat
+	participant gh as GitHub
+
+user ->> gate: Start execution for pipeline (includes plugin stage)
+gate ->> orca: Submit execution for pipeline (includes plugin stage)
+orca ->> igor: Submit the task operations of plugin stage
+igor ->> fiat: Check hasPermissions
+alt Unauthorized
+	fiat ->> igor: hasPermissions=false 
+	igor ->> orca: Fail with Forbidden
+	orca ->> gate: TERMINAL
+else Authorized
+	fiat ->> igor: hasPermissions=true
+	igor ->> orca: IN_PROGRESS
+	igor ->> gh: API calls
+	orca ->> gate: IN_PROGRESS
+end
+```
+
+### {{% heading "prereq" %}}
+
+- You are familiar with how Spinnaker's [AuthZ]({{< ref "continuous-deployment/overview/fiat-permissions-overview" >}}) works.
+- You have read the GitHub Integration Plugin [overview]({{< ref "plugins/github-integration/_index.md" >}}).
+- You have enabled Fiat in your Spinnaker or Armory CD instance integrated with an external identity provider (IDP).
+
+### How to enable AuthZ support
+
+You can enable AuthZ support per GitHub App account by setting the `permissions` block in the `github-integration-plugin.yml` file. For example:
+
+{{< highlight yaml "linenos=table,hl_lines=10-17 32-37" >}}
+github:
+  plugin:
+    accounts:
+      - name: FirstAppRepo
+        organization:  company-public
+        repository: first-app-repo
+        defaultBranch: master
+        githubAppId: 9753
+        githubAppPrivateKey: encrypted:k8s!n:spin-secrets!k:github-app-9753-privatekey
+        permissions:
+          READ: 
+            - "read-only-role"
+            - "dev-role"
+            - "ops-role"
+          EXECUTE:
+            - "dev-role"
+            - "ops-role"
+      - name: SecondAppRepo
+        organization:  company-public
+        repository: second-app-repo
+        defaultBranch: main
+        githubAppId: 9753
+        githubAppPrivateKey: encrypted:k8s!n:spin-secrets!k:github-app-9753-privatekey
+        permissions: []
+      - name: CompanyPrivateOrgAllRepos
+        organization: company-private
+        orgWideInstallation: true
+        includePublicRepositories: false
+        defaultBranch: main
+        githubAppId: 1357
+        githubAppPrivateKey: encrypted:k8s!n:spin-secrets!k:github-app-1357-privatekey
+        permissions:
+          READ:
+            - "read-only-role"
+            - "ops-role"
+          EXECUTE:
+            - "ops-role"
+{{< /highlight >}}

content/en/plugins/github-integration/commit-status-notifications.md

@@ -0,0 +1,82 @@
+---
+title: Configure GitHub Commit Status Echo notifications
+linkTitle: GitHub Notifications
+weight: 10
+description: >
+  Learn how to enable an enhanced Echo notification type which can be configured to send notifications for pipelines and/or stages statuses with custom context and description linking to the Spinnaker UI as a target URL. 
+---
+
+![Proprietary](/images/proprietary.svg) ![Beta](/images/beta.svg)
+
+
+## Configure GitHub Commit Status Echo notifications
+
+Echo is the microservice in Spinnaker which (among other functionalities) manages notifications for Spinnaker pipelines and stages.
+Using the GitHub Integration plugin you can configure Echo to create [GitHub Commit Statuses](https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status)
+in a repository by authenticating using the GitHub App accounts configured in the plugin.
+
+## How this feature works
+
+GitHub Integration plugin offers an enhanced Echo notification type which can be configured to send notifications
+for pipelines and/or stages statuses with custom context and description linking to the Spinnaker UI as a target URL.
+
+## How to enable
+
+GitHub Commit Status notifications can be enabled per GitHub App account by enabling the feature in Echo and Deck services 
+in the `github-integration-plugin.yml` file.
+
+{{< highlight yaml "linenos=table,hl_lines=7-8 14-15" >}}
+spec:
+  spinnakerConfig:
+    profiles:
+      spinnaker:
+        github:
+          plugin:
+            github-status:
+              enabled: true
+            accounts: []
+      deck:
+        settings-local.js: |
+          window.spinnakerSettings = {
+            ... (content omitted for brevity)
+            feature.githubIntegrationFlags = {
+              githubStatus: true
+            };  
+            ... (content omitted for brevity)
+          }
+{{< /highlight >}}
+
+## Migrating from Echo's default implementation
+
+Migrating from the default implementation to the GitHub Integration plugin's implementation does not require any changes in your pipelines.
+The GitHub Integration plugin's implementation will be used automatically when the feature is enabled in Echo and Deck services and the default
+implementation is disabled. To ensure a smooth migration, follow these steps:
+
+
+1. Disable the default implementation by disabling the `github-status` feature in Echo and Deck services
+
+   {{< highlight yaml "linenos=table,hl_lines=6 13" >}}
+   spec:
+     spinnakerConfig:
+       profiles:
+         echo:
+           github-status:
+             enabled: false
+             token: <PAT>
+             endpoint: https://api.github.com
+         deck:
+           settings-local.js: |
+             window.spinnakerSettings = {
+               ... (content omitted for brevity)
+               notifications.githubStatus.enabled = false;
+               ... (content omitted for brevity)
+             }
+   {{< /highlight >}}
+
+1. Enable the GitHub Integration plugin's implementation as described in the previous section.
+
+1. Ensure that you have configured the appropriate GitHub App accounts for every GitHub organisation that you want to 
+send notifications to as described in the [GitHub App accounts configuration](#github-app-accounts-configuration) section.
+
+1. Verify that the Deck UI is showing the plugin's Commit Status notification type in the notification settings for 
+your pipelines and the Commit Statuses are being created in GitHub.