docs: Adjusting redirects for moving AWS Landing Zone to Account Factory

Author: yhakbar

docs/2.0/docs/accountfactory/installation/index.md

@@ -7,18 +7,15 @@ Account Factory is automatically integrated into [new Pipelines root repositorie
 By default, Account Factory includes the following components:
 
 - 📋 An HTML form for generating workflow inputs: `.github/workflows/account-factory-inputs.html`
-  
+
 - 🏭 A workflow for generating new requests: `.github/workflows/account-factory.yml`
-  
+
 - 🗃️ A root directory for tracking account requests: `_new-account-requests`
-  
+
 - ⚙️ A YAML file for tracking account names and IDs: `accounts.yml`
 
 For detailed instructions on using these components, refer to the [Vending a New AWS Account Guide](/2.0/docs/accountfactory/guides/vend-aws-account).
 
 ## Configuring account factory
 
 Account Factory is fully operational for vending new accounts without requiring any configuration changes. However, a [comprehensive reference for all configuration options is available here](/2.0/reference/accountfactory/configurations), allowing you to customize values and templates for generating Infrastructure as Code (IaC) for new accounts.
-
- 
-

docs/2.0/docs/pipelines/installation/authoverview.md

@@ -1,12 +1,13 @@
 # Authenticating Gruntwork Pipelines
 
 Gruntwork Pipelines requires authentication with GitHub/GitLab to perform various functions, including:
-* Downloading Gruntwork code, such as the Pipelines binary and Terraform modules, from the `gruntwork-io` GitHub organization.
-* Interacting with your repositories, such as:
-  * Creating pull requests.
-  * Commenting on pull requests.
-  * Creating new repositories via Account Factory.
-  * Updating repository settings, such as enforcing branch protection, via Account Factory.
+
+- Downloading Gruntwork code, such as the Pipelines binary and Terraform modules, from the `gruntwork-io` GitHub organization.
+- Interacting with your repositories, such as:
+  - Creating pull requests.
+  - Commenting on pull requests.
+  - Creating new repositories via Account Factory.
+  - Updating repository settings, such as enforcing branch protection, via Account Factory.
 
 Gruntwork provides two authentication methods: a [GitHub App](/2.0/docs/pipelines/installation/viagithubapp.md) and CI Users ([Machine Users](/2.0/docs/pipelines/installation/viamachineusers.md)) with personal access tokens for Pipelines.
 
@@ -15,11 +16,14 @@ Both approaches support the core functionality of Pipelines. However, the GitHub
 ## Summary of authentication mechanisms for GitHub
 
 **Advantages of the GitHub App**:
+
 - Simplified setup process.
 - Access to enhanced features and functionality.
 - Improved user experience during regular operations.
 - Reduced maintenance, as there is no need to install, maintain, or rotate powerful tokens.
 
 **Advantages of Machine Users**:
+
 - Compatibility with on-premises GitHub Enterprise installations that cannot interact with third-party servers (e.g., Gruntwork's backend).
 - Provides a fallback solution to ensure Pipelines continue functioning in the unlikely event of an outage affecting the Gruntwork-hosted backend that powers the GitHub App.
+- Allows GitLab customers to download the Pipelines binary from GitLab CI Pipelines.

docs/2.0/docs/pipelines/installation/viagithubapp.md

@@ -13,6 +13,7 @@ The [Gruntwork.io GitHub App](https://github.com/apps/gruntwork-io) is a [GitHub
 At this time Gruntwork does not provide an app for GitLab, this page is only relevant for Gruntwork Pipelines users installing in GitHub.
 
 :::
+
 ## Overview
 
 There are three major components to keep in mind when working with the Gruntwork.io GitHub App:
@@ -28,6 +29,7 @@ The Gruntwork.io GitHub App is the principal that Gruntwork products will utiliz
 #### Required Permissions
 
 As of 2024/09/10, the Gruntwork.io GitHub App requests the following permissions:
+
 - **Read access to Actions**: Allows the app to read GitHub Actions artifacts.
 - **Write access to Administration**: Allows the app to create new repositories, and add teams as collaborators to repositories.
 - **Write access to Contents**: Allows the app to read and write repository contents.
@@ -40,13 +42,15 @@ As of 2024/09/10, the Gruntwork.io GitHub App requests the following permissions
 
   Gruntwork.io requests all of these permissions because it requires them for different operations. Unfortunately, the way GitHub apps work prevents us from requesting permissions on a more granular basis. Know that the GitHub App Service will scope down its permissions whenever possible to the minimum required for the operation at hand.
 
-  The level of granularity available to customers when configuring the GitHub App installation is to either install the app on a per-repository basis or on an entire organization. Our recommendation is as follows:
+  The level of granularity available to customers when configuring the GitHub App installation is to either install the app on a per-repository basis or on an entire organization. Our recommendation is as follows for Account Factory customers:
+
+  - For non-enterprise customers, allow the app for `infrastructure-live-root` repository and (if in-use) `infrastructure-live-access-control` and `infrastructure-catalog`.
 
-  * For non-enterprise customers, allow the app for `infrastructure-live-root` repository and (if in-use) `infrastructure-live-access-control` and `infrastructure-catalog`.
-  * For enterprise customers, allow the app to have access to the entire organization.
+  - For enterprise customers, allow the app to have access to the entire organization.
 
-The reasoning for requiring entire-organization access for enterprise customers is that if you are using Account Factory to create delegated repositories then Account Factory will be creating, and then immediately modifying, new repositories in automated flows, which means it needs access to new repos as soon as they are created which is only possible with entire organization permission.
+  For non-Account Factory customers, we recommend installing the app on a per-repository basis.
 
+  The reasoning for requiring entire-organization access for enterprise customers is that if you are using Account Factory to create delegated repositories then Account Factory will be creating, and then immediately modifying, new repositories in automated flows, which means it needs access to new repos as soon as they are created which is only possible with entire organization permission.
 
   If you are unsure how to proceed here, reach out to Gruntwork Support for guidance.
 
@@ -108,7 +112,7 @@ The GitHub App Service is used by two major clients:
 
 2. **Gruntwork Pipelines**
 
-   The main client for the Gruntwork.io App, and where most of the value is derived. Pipelines uses the GitHub App Service to acquire the relevant access for interacting with GitHub resources on behalf of the user. Access control rules are enforced here to ensure that only the level of access required, and explicitly specified in the Gruntwork Developer Portal can be used by Pipelines to interact with GitHub resources on behalf of the user.
+   The main client for the Gruntwork.io App, and where most of the value is derived. Pipelines uses the GitHub App Service to acquire the relevant access for interacting with GitHub resources on behalf of the user. Access control rules are enforced here to ensure that only the level of access required (and explicitly specified in the Gruntwork Developer Portal) can be used by Pipelines to interact with GitHub resources on behalf of the user.
 
    For example, while the Gruntwork.io GitHub App does have permissions to create new repositories, Pipelines will only do so if a workflow originating from a configured `infrastructure-live-root` repository requests it.
 
@@ -118,19 +122,19 @@ The availability of the Gruntwork.io GitHub App is something Gruntwork will ende
 
 Any downtime of Gruntwork services will not impact the ability of your team to manage infrastructure using Gruntwork products.
 
-#### App Only Features
+### App Only Features
 
 The following features of the Gruntwork.io GitHub App will be unavailable during downtime:
 
 - **GitHub App Linking**: In order to link a Gruntwork.io GitHub App installation to the [Gruntwork Developer Portal](https://app.gruntwork.io), the service backing the GitHub app must be available and operating correctly.
 - **Gruntwork Pipelines Comments**: While Pipelines will allow for IaC updates in a degraded state without the availability of the GitHub App, comments are a feature that rely on the availability of the app for the best experience.
 - **Gruntwork Pipelines Drift Detection**: Drift detection requires the availability of the GitHub App to function correctly.
 
-#### Fallback
+### Fallback
 
-In order to ensure that the availability of the Gruntwork.io GitHub App is not something that can impair the ability of users to drive infrastructure updates, the legacy mechanism of authenticating with GitHub using [Machine users](/2.0/docs/pipelines/installation/viamachineusers.md) is still supported.
+In order to ensure that the availability of the Gruntwork.io GitHub App is not something that can impair the ability of users to drive infrastructure updates, users can also authenticate with GitHub using [Machine users](/2.0/docs/pipelines/installation/viamachineusers.md).
 
-Configuring the `PIPELINES_READ_TOKEN`, `INFRA_ROOT_WRITE_TOKEN` and `ORG_REPO_ADMIN_TOKEN` where necessary (following the documentation linked above) will result in Pipelines using the legacy mechanism to authenticate with GitHub, rather than the Gruntwork.io GitHub App.
+Configuring the `PIPELINES_READ_TOKEN`, `INFRA_ROOT_WRITE_TOKEN` and `ORG_REPO_ADMIN_TOKEN` where necessary (following the documentation linked above) will result in Pipelines using the machine users mechanism to authenticate with GitHub, rather than the Gruntwork.io GitHub App.
 
 Using these fallback tokens will ensure that Pipelines can continue to perform operations like:
 
@@ -160,7 +164,7 @@ To install the Gruntwork.io GitHub App in your organization follow these steps.
 
 ## Configuration
 
-<h3>Infrastructure Live Root Repositories</h3>
+### Infrastructure Live Root Repositories
 
 DevOps Foundations treats certain repositories as especially privileged in order to perform critical operations like vending new AWS accounts and creating new repositories. These repositories are called "infrastructure live root repositories" and you can configure them in the [GitHub Account section](https://app.gruntwork.io/account?scroll_to=github-app) for your organization in the Gruntwork developer portal **if you are a designated administrator**.
 
@@ -174,7 +178,7 @@ For more information, see the [relevant architecture documentation](/2.0/docs/pi
 
 ## Frequently Asked Questions
 
-#### How do I find my Gruntwork.io GitHub App installation ID?
+### How do I find my Gruntwork.io GitHub App installation ID?
 
 You can find the installation ID of the Gruntwork.io GitHub App in the URL of the installation page.