Skip to content

Commit

Permalink
fix: Fix project labels (#1107)
Browse files Browse the repository at this point in the history 
Co-authored-by: Samir Ribeiro <42391123+Samir-Cit@users.noreply.github.com>
Co-authored-by: Andrew Peabody <andrewpeabody@google.com>
  • Loading branch information
@mariammartins @Samir-Cit @apeabody
3 people authored Apr 9, 2024
1 parent 0a03623 commit eb28ecb
Show file tree
Hide file tree
Showing 120 changed files with 544 additions and 504 deletions.
78 changes: 39 additions & 39 deletions 0-bootstrap/README-GitHub.md
View file

Large diffs are not rendered by default.

68 changes: 34 additions & 34 deletions 0-bootstrap/README-GitLab.md
View file

Large diffs are not rendered by default.

50 changes: 25 additions & 25 deletions 0-bootstrap/README-Jenkins.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -305,7 +305,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git clone <YOUR_NEW_REPO-gcp-org> gcp-org
```

1. Navigate into the repo and change to a non-production branch. All subsequent
1. Navigate into the repo and change to a nonproduction branch. All subsequent
steps assume you are running them from the `gcp-org` directory. If
you run them from another directory, adjust your copy paths accordingly.

Expand Down Expand Up @@ -411,7 +411,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git clone <YOUR_NEW_REPO-gcp-environments> gcp-environments
```

1. Navigate into the repo and change to a non-production branch. All subsequent
1. Navigate into the repo and change to a nonproduction branch. All subsequent
steps assume you are running them from the `gcp-environments` directory. If
you run them from another directory, adjust your copy paths accordingly.

Expand Down Expand Up @@ -491,11 +491,11 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. Merge changes to non-production with.
1. Merge changes to nonproduction with.

```bash
git checkout -b non-production
git push --set-upstream origin non-production
git checkout -b nonproduction
git push --set-upstream origin nonproduction
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
Expand All @@ -517,7 +517,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git clone <YOUR_NEW_REPO-gcp-networks> gcp-networks
```

1. Navigate into the repo and change to a non-production branch. All subsequent
1. Navigate into the repo and change to a nonproduction branch. All subsequent
steps assume you are running them from the `gcp-networks` directory. If
you run them from another directory, adjust your copy paths accordingly.

Expand Down Expand Up @@ -591,7 +591,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git commit -m 'Initialize networks repo'
```

1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.
1. You must manually plan and apply the `shared` environment (only once) since the `development`, `nonproduction` and `production` environments depend on it.
1. To use the `validate` option of the `tf-wrapper.sh` script, please follow the [instructions](https://cloud.google.com/docs/terraform/policy-validation/validate-policies#install) to install the terraform-tools component.
1. Also update `backend.tf` with your backend bucket from gcp-bootstrap output.

Expand Down Expand Up @@ -644,7 +644,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. After production has been applied, apply development and non-production.
1. After production has been applied, apply development and nonproduction.
1. Merge changes to development

```bash
Expand All @@ -653,11 +653,11 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. Merge changes to non-production.
1. Merge changes to nonproduction.

```bash
git checkout -b non-production
git push --set-upstream origin non-production
git checkout -b nonproduction
git push --set-upstream origin nonproduction
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
Expand All @@ -670,7 +670,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git clone <YOUR_NEW_REPO-gcp-networks> gcp-networks
```

1. Navigate into the repo and change to a non-production branch. All subsequent
1. Navigate into the repo and change to a nonproduction branch. All subsequent
steps assume you are running them from the `gcp-networks` directory. If
you run them from another directory, adjust your copy paths accordingly.

Expand Down Expand Up @@ -744,7 +744,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git commit -m 'Initialize networks repo'
```

1. You must manually plan and apply the `shared` environment (only once) since the `development`, `non-production` and `production` environments depend on it.
1. You must manually plan and apply the `shared` environment (only once) since the `development`, `nonproduction` and `production` environments depend on it.
1. To use the `validate` option of the `tf-wrapper.sh` script, please follow the [instructions](https://cloud.google.com/docs/terraform/policy-validation/validate-policies#install) to install the terraform-tools component.
1. Also update `backend.tf` with your backend bucket from gcp-bootstrap output.

Expand Down Expand Up @@ -797,7 +797,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. After production has been applied, apply development and non-production.
1. After production has been applied, apply development and nonproduction.
1. Merge changes to development

```bash
Expand All @@ -806,11 +806,11 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. Merge changes to non-production.
1. Merge changes to nonproduction.

```bash
git checkout -b non-production
git push --set-upstream origin non-production
git checkout -b nonproduction
git push --set-upstream origin nonproduction
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
Expand All @@ -823,7 +823,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
git clone <YOUR_NEW_REPO-gcp-projects> gcp-projects
```

1. Navigate into the repo and change to a non-production branch. All subsequent
1. Navigate into the repo and change to a nonproduction branch. All subsequent
steps assume you are running them from the `gcp-projects` directory. If
you run them from another directory, adjust your copy paths accordingly.

Expand Down Expand Up @@ -872,11 +872,11 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
mv common.auto.example.tfvars common.auto.tfvars
mv shared.auto.example.tfvars shared.auto.tfvars
mv development.auto.example.tfvars development.auto.tfvars
mv non-production.auto.example.tfvars non-production.auto.tfvars
mv nonproduction.auto.example.tfvars nonproduction.auto.tfvars
mv production.auto.example.tfvars production.auto.tfvars
```

1. See any of the envs folder [README.md](../4-projects/business_unit_1/production/README.md) files for additional information on the values in the `common.auto.tfvars`, `development.auto.tfvars`, `non-production.auto.tfvars`, and `production.auto.tfvars` files.
1. See any of the envs folder [README.md](../4-projects/business_unit_1/production/README.md) files for additional information on the values in the `common.auto.tfvars`, `development.auto.tfvars`, `nonproduction.auto.tfvars`, and `production.auto.tfvars` files.
1. See any of the shared folder [README.md](../4-projects/business_unit_1/shared/README.md) files for additional information on the values in the `shared.auto.tfvars` file.
1. Use `terraform output` to get the backend bucket value from gcp-bootstrap output.

Expand All @@ -899,7 +899,7 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
for i in `find . -name 'backend.tf'`; do sed -r -i "s/UPDATE_ME|UPDATE_PROJECTS_BACKEND/${backend_bucket}/" $i; done
```

1. You need to manually plan and apply only once the `shared` environments since `development`, `non-production`, and `production` depend on it.
1. You need to manually plan and apply only once the `shared` environments since `development`, `nonproduction`, and `production` depend on it.
1. Use `terraform output` to get the Cloud Build project ID and the projects step Terraform Service Account from gcp-bootstrap output. An environment variable `GOOGLE_IMPERSONATE_SERVICE_ACCOUNT` will be set using the Terraform Service Account to enable impersonation.

```bash
Expand Down Expand Up @@ -954,12 +954,12 @@ Here you will configure a VPN Network tunnel to enable connectivity between the
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
1. After development has been applied, apply non-production.
1. Merge changes to non-production branch.
1. After development has been applied, apply nonproduction.
1. Merge changes to nonproduction branch.

```bash
git checkout -b non-production
git push --set-upstream origin non-production
git checkout -b nonproduction
git push --set-upstream origin nonproduction
```

1. Review the apply output in your Controller's web UI (you might want to use the option to "Scan Multibranch Pipeline Now" in your Jenkins Controller UI).
Expand Down
Loading

0 comments on commit eb28ecb

Please sign in to comment.