Skip to content

Commit f5a004b

Browse files
committed
chore: docs
1 parent 6391ee4 commit f5a004b

File tree

4 files changed

+66
-22
lines changed

4 files changed

+66
-22
lines changed

docs/.vitepress/config.ts

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,7 @@ export default defineConfig({
2020
{
2121
text: "Deployment", items: [
2222
{ text: "Helm", link: "/docs/deployment/helm" },
23-
{ text: "Docker", link: "/docs/deployment/docker" },
24-
{ text: "Verify deployment", link: "/docs/deployment/verify" }
23+
{ text: "Docker", link: "/docs/deployment/docker" }
2524
]
2625
},
2726
{

docs/docs/deployment/docker.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,3 +30,32 @@ Afterwards start the application:
3030
```sh
3131
docker compose up -d
3232
```
33+
34+
## Verifying Deployment
35+
36+
To verify your deployment you can now run the dockerized integration tests using `ghcr.io/onelitefeathernet/feedback-fusion-integrtion:<version>`.
37+
The image requires the following environment variables to be set:
38+
39+
| Key | Description |
40+
|-----------------|-----------------------------------------------------|
41+
| OIDC_PROVIDER | URL of the OIDC provider |
42+
| OIDC_CLIENT_ID | The client ID |
43+
| OIDC_CLIENT_SECRET | The client secret |
44+
| GRPC_ENDPOINT | The endpoint of the deployed application |
45+
46+
### Run the tests
47+
48+
```sh
49+
docker run --network <network> \
50+
-e OIDC_PROVIDER=<oidc_provider> \
51+
-e OIDC_CLIENT_ID=<oidc_client_id> \
52+
-e OIDC_CLIENT_SECRET=<oidc_client_secret> \
53+
-e GRPC_ENDPOINT=<grpc_endpoint>
54+
--name feedback-fusion-integration-test \
55+
--rm \
56+
ghcr.io/onelitefeathernet/feedback-fusion-integrtion:<version>
57+
```
58+
59+
### On finish
60+
61+
You should now reset your database as the integration test does not delete everything it created.

docs/docs/deployment/helm.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,7 @@ Refer to the [configuration documentation](/docs/configuration) for the fields t
6060
| `feedbackFusion.preset.create` | Create preset configuration | `false` |
6161
| `feedbackFusion.preset.data` | Preset data | `{}` [Preset configuration](/docs/configuration#presets) |
6262
| `feedbackFusion.config.secret` | Name of the secret containing configuration | `feedback-fusion-config` |
63+
| `feedbackFusion.testSecret` | Name of the secret containing configuration for the integration test | `feedback-fusion-integration-test` |
6364

6465
## Install
6566

@@ -68,3 +69,38 @@ helm install feedback-fusion feedback-fusion/feedback-fusion --wait --atomic
6869
```
6970

7071
Your instance should now be up and running :)
72+
73+
## Verifying Deployment with Helm Test
74+
75+
To verify the deployment of the Helm chart, you can use the `helm test` command. However, before running the test, a secret must be created with the name `feedback-fusion-integration-test`. Alternatively, the name of another secret can be set via the Helm value `feedbackFusion.testSecret`.
76+
77+
The secret should contain the following values:
78+
79+
| Key | Description |
80+
|-----------------|-----------------------------------------------------|
81+
| OIDC_PROVIDER | URL of the OIDC provider |
82+
| OIDC_CLIENT_ID | The client ID |
83+
| OIDC_CLIENT_SECRET | The client secret |
84+
| GRPC_ENDPOINT | The endpoint of the deployed application |
85+
86+
### Creating the Secret
87+
88+
To create the secret, you can use the following `kubectl` command:
89+
90+
```sh
91+
kubectl create -n <namespace> secret generic feedback-fusion-integration-test \
92+
--from-literal=OIDC_PROVIDER=<oidc_provider_url> \
93+
--from-literal=OIDC_CLIENT_ID=<client_id> \
94+
--from-literal=OIDC_CLIENT_SECRET=<client_secret> \
95+
--from-literal=GRPC_ENDPOINT=<grpc_endpoint>
96+
```
97+
98+
### Run the tests
99+
100+
```sh
101+
helm test -n <namespace> <release>
102+
```
103+
104+
### On finish
105+
106+
You should now reset your database as the integration test does not delete everything it created.

docs/docs/deployment/verify.md

Lines changed: 0 additions & 20 deletions
This file was deleted.

0 commit comments

Comments
 (0)