Skip to content

Commit

Permalink
Copy edits
Browse files Browse the repository at this point in the history
  • Loading branch information
kellie-freeman committed Sep 16, 2024
1 parent e53791c commit a766491
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 15 deletions.
2 changes: 0 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@ This document provides guidelines for contributing to the CloudBees CD/RO add-on

Validate your changes inside the blueprint agent, as described in [Dockerfile](blueprints/Dockerfile) For example, it can be used to run `make dBuildAndRun`.

<!---
## Report bugs and feature requests

CloudBees welcomes you to use the GitHub issue tracker to report bugs or suggest features.
Expand Down Expand Up @@ -43,7 +42,6 @@ To submit a pull request:

> [!IMPORTANT]
> If you make updates to embedded repository (e.g. CasC bundles), you must push the changes to the public upstream (repository/branch) before running `terraform apply` locally. The endpoint and/or branch can be updated via `set-casc-location` from the companion [Makefile](Makefile).
-->
## Pre-commits: Linting, Formatting and Secrets Scanning

Expand Down
26 changes: 13 additions & 13 deletions blueprints/02-at-scale/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,10 @@ Once you have familiarized yourself with the [CloudBees CD/RO blueprint: Get sta
When preparing to deploy, you must complete the following steps:

1. Customize your Terraform values by copying `.auto.tfvars.example` to `.auto.tfvars`.
2. Customize your secrets file by copying `flow_db_secrets-values.yml.example` to `flow_db_secrets-values.yml`.
3. If using the Terraform variable `suffix` for this blueprint, the Amazon `S3 Bucket Access settings` > `S3 Bucket Name` must be updated.
4. Initialize the root module and any associated configuration for providers.
5. Create the resources and deploy CloudBees CD/RO to an EKS cluster. Refer to [Amazon EKS Blueprints for Terraform - Deploy](https://aws-ia.github.io/terraform-aws-eks-blueprints/getting-started/#deploy).
1. Customize your secrets file by copying `flow_db_secrets-values.yml.example` to `flow_db_secrets-values.yml`.
1. If using the Terraform variable `suffix` for this blueprint, the Amazon `S3 Bucket Access settings` > `S3 Bucket Name` must be updated.
1. Initialize the root module and any associated configuration for providers.
1. Create the resources and deploy CloudBees CD/RO to an EKS cluster. Refer to [Amazon EKS Blueprints for Terraform - Deploy](https://aws-ia.github.io/terraform-aws-eks-blueprints/getting-started/#deploy).

For more information, refer to [The Core Terraform Workflow](https://www.terraform.io/intro/core-workflow) documentation.

Expand All @@ -101,8 +101,8 @@ Once you can access the Kubernetes API from your terminal, complete the followin
```sh
terraform output cbcd_url
```
2. To access CloudBees CD/RO, paste the output of the previous command into a web browser.
3. Issue the following command to retrieve the initial administrative user password to sign in to CloudBees CD/RO:
1. To access CloudBees CD/RO, paste the output of the previous command into a web browser.
1. Issue the following command to retrieve the initial administrative user password to sign in to CloudBees CD/RO:

```sh
eval $(terraform output --raw cbcd_password)
Expand All @@ -116,7 +116,7 @@ Once you can access the Kubernetes API from your terminal, complete the followin
```sh
eval $(terraform output -raw rds_backup_cmd)
```
2. Issue the following command to restore the RDS instance from the snapshot:
1. Issue the following command to restore the RDS instance from the snapshot:

```sh
eval $(terraform output -raw rds_restore_cmd)
Expand All @@ -129,23 +129,23 @@ Once you can access the Kubernetes API from your terminal, complete the followin
```sh
eval $(terraform output --raw velero_backup_schedule_team_cd)
```
2. Issue the following command to take an on-demand Velero backup for a specific point in time for `Team CD` based on the schedule definition:
1. Issue the following command to take an on-demand Velero backup for a specific point in time for `Team CD` based on the schedule definition:

```sh
eval $(terraform output --raw velero_backup_on_demand_team_cd)
```

3. Issue the following command to restore from the last backup:
1. Issue the following command to restore from the last backup:

```sh
eval $(terraform output --raw velero_restore_team_cd)
```

4. Issue the following command to restore from an Amazon EFS access point, that matches the CloudBees CD/RO PVC:
1. Issue the following command to restore from an Amazon EFS access point, that matches the CloudBees CD/RO PVC:

```sh
eval $(terraform output --raw efs_access_points) | . jq .AccessPoints[].RootDirectory.Path
```
```sh
eval $(terraform output --raw efs_access_points) | . jq .AccessPoints[].RootDirectory.Path
```

## Destroy

Expand Down

0 comments on commit a766491

Please sign in to comment.