You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/with-backstage/README.md
+26-20Lines changed: 26 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -5,24 +5,30 @@ Provisions the AWS reference architecture connected to Humanitec and installs Ba
5
5
## Prerequisites
6
6
7
7
* The same prerequisites as the [base reference architecture](../../README.md#prerequisites), plus the following items.
8
-
* A GitHub organization and permission to create new repositories in it. Go to https://github.com/account/organizations/new to create a new org (the "Free" option is fine). Note: is has to be an organization, a free account is not sufficient.
8
+
* A GitHub organization and permission to create new repositories in it. Go to <https://github.com/account/organizations/new> to create a new org (the "Free" option is fine). Note: is has to be an organization, a free account is not sufficient.
9
9
* Create a classic github personal access token with `repo`, `workflow`, `delete_repo` and `admin:org` scope [here](https://github.com/settings/tokens).
10
10
* Set the `GITHUB_TOKEN` environment variable to your token.
11
-
```
11
+
12
+
```bash
12
13
export GITHUB_TOKEN="my-github-token"
13
14
```
15
+
14
16
* Set the `GITHUB_ORG_ID` environment variable to your GitHub organization ID.
15
-
```
17
+
18
+
```bash
16
19
export GITHUB_ORG_ID="my-github-org-id"
17
20
```
21
+
18
22
*[Node.js](https://nodejs.org) installed locally.
19
-
* Install the GitHub App for Backstage into your GitHub organization using `node create-gh-app/index.js`. Follow the instructions.
20
-
* “All repositories” ~> Install
21
-
* “Okay, […] was installed on the […] account.” ~> You can close the window and server.
23
+
* Install the GitHub App for Backstage into your GitHub organization
24
+
* Run `docker run --rm -it -e GITHUB_ORG_ID -v $(pwd):/pwd -p 127.0.0.1:3000:3000 ghcr.io/humanitec-architecture/create-gh-app` ([image source](https://github.com/humanitec-architecture/create-gh-app/)) and follow the instructions:
25
+
* “All repositories” ~> Install
26
+
* “Okay, […] was installed on the […] account.” ~> You can close the window and server.
22
27
23
28
## Usage
24
29
25
30
Follow the same steps as for the [base layer](../../README.md#usage), applying these modifications:
31
+
26
32
* Execute `cd ./examples/with-backstage` after cloning the repo. Execute all subsequent commands in this directory.
27
33
* In particular, use the `./examples/with-backstage/terraform.tfvars.example` file as the basis for your `terraform.tfvars` file. It defines additional variables needed to setup and configure Backstage.
28
34
@@ -32,31 +38,38 @@ Check for the existence of key elements of the backstage module. This is a subse
32
38
33
39
1. Perform the [verification steps of the base installation](../../README.md) if you have not already done so.
34
40
2. Verify the existence of the Backstage Application in your Humanitec Organization:
You can also check for the Application in the [Humanitec Platform Orchestrator UI](https://app.humanitec.io).
44
54
45
55
3. Connect to your EKS cluster via `kubectl`. See the [AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html) or use this command:
4. Get the elements in the newly created Kubernetes namespace:
62
+
50
63
```
51
64
kubectl get all -n backstage-development
52
65
```
66
+
53
67
You should see
54
-
- a `deployment`, `replicaset`, running `pod`, and `service` for Backstage
55
-
- a `statefulset`, running `pod`, and `service` for PostgreSQL database used by Backstage.
68
+
* a `deployment`, `replicaset`, running `pod`, and `service` for Backstage
69
+
* a `statefulset`, running `pod`, and `service` for PostgreSQL database used by Backstage.
56
70
57
71
Note: it may take up to ten minutes after the `terraform apply` completed until you actually see those resources. The Backstage application needs to built and deployed via a GitHub action out of the newly created repository in your GitHub organization.
58
72
59
-
60
73
## Cleaning up
61
74
62
75
Once you are finished with the reference architecture, you can remove all provisioned infrastrcuture and the resource definitions created in Humanitec with the following:
@@ -75,7 +88,9 @@ Once you are finished with the reference architecture, you can remove all provis
75
88
| terraform | >= 1.3.0 |
76
89
| aws |~> 5.17 |
77
90
| github |~> 5.38 |
91
+
| helm |~> 2.12 |
78
92
| humanitec |~> 1.0 |
93
+
| kubernetes |~> 2.25 |
79
94
| random |~> 3.5 |
80
95
81
96
### Providers
@@ -92,12 +107,8 @@ Once you are finished with the reference architecture, you can remove all provis
0 commit comments