fix: Removing unnecessary GitLab content

Author: yhakbar

docs/2.0/docs/pipelines/installation/addinggitlabrepo.mdx

@@ -330,109 +330,6 @@ terragrunt run --all --non-interactive --provider-cache apply
 
 :::
 
-## Creating `.gruntwork` HCL configurations
-
-Create [HCL configurations](/2.0/reference/pipelines/configurations-as-code/) in the `.gruntwork` directory in the root of your `infrastructure-live` repository to tell Pipelines how you plan to organize your infrastructure, and how you plan to have Pipelines authenticate with your cloud provider(s).
-
-### The `repository` block
-
-The core configuration that you'll want to start with is the `repository` block. This block tells Pipelines which branch has the "live" infrastructure you want provisioned. When you merge IaC to this branch, Pipelines will be triggered to update your infrastructure accordingly.
-
-```hcl title=".gruntwork/repository.hcl"
-repository {
-  deploy_branch_name = "main"
-}
-```
-
-:::note Progress Checklist
-
-<PersistentCheckbox id="create-repository-hcl" label="Create a new `.gruntwork/repository.hcl` file in the root of your `infrastructure-live` repository with the contents above." />
-<PersistentCheckbox id="edit-repository-deploy-branch-name" label="Edit the value of `deploy_branch_name` in `.gruntwork/repository.hcl` if necessary." />
-
-:::
-
-### The `environment` block
-
-Next, you'll want to define the environments you want to manage with Pipelines using the [`environment` block](/2.0/reference/pipelines/configurations-as-code/api#environment-block).
-
-For each environment, you'll want to define a [`filter` block](/2.0/reference/pipelines/configurations-as-code/api#filter-block) that tells Pipelines which units are part of that environment. You'll also want to define an [`authentication` block](/2.0/reference/pipelines/configurations-as-code/api#authentication-block) that tells Pipelines how to authenticate with your cloud provider(s) for that environment.
-
-```hcl title=".gruntwork/environment-an-aws-account.hcl"
-environment "an_aws_account" {
-  filter {
-    paths = ["an-aws-account/*"]
-  }
-
-  authentication {
-    aws_oidc {
-      account_id = "123456789012"
-      plan_iam_role_arn = "arn:aws:iam::123456789012:role/pipelines-plan"
-      apply_iam_role_arn = "arn:aws:iam::123456789012:role/pipelines-apply"
-    }
-  }
-}
-```
-
-:::tip
-
-Learn more about how Pipelines authenticates to AWS in the [Authenticating to AWS](/2.0/docs/pipelines/concepts/cloud-auth/aws) page.
-
-:::
-
-:::tip
-
-Check out the [aws block](/2.0/reference/pipelines/configurations-as-code/#aws-blocks) for more information on how to configure Pipelines to authenticate with AWS conveniently.
-
-:::
-
-:::note Progress Checklist
-
-<PersistentCheckbox id="create-aws-environment-hcl" label="Create a new `.gruntwork/environment-an-aws-account.hcl` file in the root of your `infrastructure-live` repository with the contents above." />
-<PersistentCheckbox id="rename-aws-environment-hcl" label="Rename the file to match the name of the environment you want to manage with pipelines." />
-<PersistentCheckbox id="edit-aws-environment-label" label="Edit the label of the `environment` block from `an_aws_account` to the name of the environment you want to manage with pipelines." />
-<PersistentCheckbox id="edit-aws-filter-paths" label="Edit the value of `paths` in the `filter` block so that the glob matches the path to the units you want to manage with Pipelines as part of that environment." />
-<PersistentCheckbox id="edit-aws-account-id" label="Edit the value of `account_id` in the `aws_oidc` block so that it matches the AWS account ID of the account you want to authenticate with." />
-<PersistentCheckbox id="edit-aws-plan-iam-role-arn" label="Edit the value of `plan_iam_role_arn` and `apply_iam_role_arn` in the `aws_oidc` block so that they match the IAM roles you want to assume for plans and applies for that environment." />
-
-:::
-
-## Creating `.gitlab-ci.yml`
-
-Create a `.gitlab-ci.yml` file in the root of your `infrastructure-live` repository with the following content:
-
-```yaml title=".gitlab-ci.yml"
-include:
-  - component: gitlab.com/gruntwork-io/pipelines-workflows/gitlab-ci@v4
-    inputs:
-      stage: pipelines
-```
-
-:::info
-
-**For custom GitLab instances only**: If you are using a custom GitLab instance, you must update the component reference to point to your forked version of the pipelines-workflows project:
-
-```yaml title=".gitlab-ci.yml"
-include:
-  - component: your-gitlab-instance.com/your-group/pipelines-workflows/gitlab-ci@v4
-    inputs:
-      stage: pipelines
-```
-
-:::
-
-:::tip
-
-You can read the [Pipelines GitLab CI Component](https://gitlab.com/gruntwork-io/pipelines-workflows/-/blob/main/templates/gitlab-ci.yml) to learn how this GitLab CI component calls the Pipelines CLI to run your pipelines.
-
-:::
-
-:::note Progress Checklist
-
-<PersistentCheckbox id="create-gitlab-ci-yml" label="Create a new `.gitlab-ci.yml` file in the root of your `infrastructure-live` repository with the contents above." />
-<PersistentCheckbox id="update-gitlab-ci-component-reference" label="If using a custom GitLab instance, update the component reference to point to your forked pipelines-workflows project." />
-
-:::
-
 ## Commit and push your changes
 
 Commit and push your changes to your repository.