chore: remove useless tests after deployment

Author: Randoooom

.github/workflows/nightly.yml

@@ -124,29 +124,6 @@ jobs:
           push: true
           tags: ghcr.io/onelitefeathernet/feedback-fusion-dashboard:nightly
 
-  integration: 
-    needs: [docker]
-    name: dockerize integration test 
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout Sources
-        uses: actions/checkout@v4
-
-      - name: Login into repository
-        uses: docker/login-action@v3
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          push: true
-          file: tests/integration/Dockerfile
-          tags: ghcr.io/onelitefeathernet/feedback-fusion-integration:nightly
-
   docs: 
     needs: [docker]
     name: docs 

.github/workflows/release.yml

@@ -129,34 +129,6 @@ jobs:
           push: true
           tags: ghcr.io/onelitefeathernet/feedback-fusion-dashboard:${{env.VERSION}},ghcr.io/onelitefeathernet/feedback-fusion-dashboard:latest
 
-  integration: 
-    needs: [docker]
-    name: dockerize integration test 
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout Sources
-        uses: actions/checkout@v4
-
-      - name: Extract version
-        run: |
-          VERSION=$(grep '^version = ' Cargo.toml | sed -E 's/version = "(.*)"/\1/')
-          echo "VERSION=$VERSION" >> $GITHUB_ENV
-
-      - name: Login into repository
-        uses: docker/login-action@v3
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          push: true
-          file: tests/integration/Dockerfile
-          tags: ghcr.io/onelitefeathernet/feedback-fusion-integration:${{env.VERSION}},ghcr.io/onelitefeathernet/feedback-fusion-integration:latest
-
   docs: 
     needs: [docker]
     name: docs 

charts/feedback-fusion/templates/deployment.yaml

@@ -40,7 +40,7 @@ spec:
               protocol: TCP
           env:
             - name: RUST_LOG 
-              value: INFO 
+              value: {{ .Values.feedbackFusion.log }}
             - name: FEEDBACK_FUSION_CONFIG
               value: /etc/config/config.yaml
           livenessProbe:

charts/feedback-fusion/templates/tests/integration-tests.yaml

@@ -93,9 +93,7 @@ tolerations: []
 affinity: {}
 
 feedbackFusion:
+  log: INFO
   config: 
     # with config.yaml as key
     secret: feedback-fusion-config
- 
-  testSecret: feedback-fusion-integration-test
-

charts/feedback-fusion/values.yaml

@@ -32,32 +32,3 @@ Afterwards start the application:
 ```sh 
 docker compose up -d
 ```
-
-## Verifying Deployment
-
-To verify your deployment you can now run the dockerized integration tests using `ghcr.io/onelitefeathernet/feedback-fusion-integrtion:<version>`.
-The image requires the following environment variables to be set:
-
-| Key             | Description                                         |
-|-----------------|-----------------------------------------------------|
-| OIDC_PROVIDER   | URL of the OIDC provider                           |
-| OIDC_CLIENT_ID  | The client ID                                       |
-| OIDC_CLIENT_SECRET | The client secret                               |
-| GRPC_ENDPOINT   | The endpoint of the deployed application            |
-
-### Run the tests 
-
-```sh 
-docker run --network <network> \
-    -e OIDC_PROVIDER=<oidc_provider> \
-    -e OIDC_CLIENT_ID=<oidc_client_id> \
-    -e OIDC_CLIENT_SECRET=<oidc_client_secret> \
-    -e GRPC_ENDPOINT=<grpc_endpoint> 
-    --name feedback-fusion-integration-test \
-    --rm \
-    ghcr.io/onelitefeathernet/feedback-fusion-integrtion:<version>
-```
-
-### On finish
-
-You should now reset your database as the integration test does not delete everything it created.

docs/docs/deployment/docker.md

@@ -69,38 +69,3 @@ helm install feedback-fusion feedback-fusion/feedback-fusion --wait --atomic
 ```
 
 Your instance should now be up and running :)
-
-## Verifying Deployment with Helm Test
-
-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`.
-
-The secret should contain the following values:
-
-| Key             | Description                                         |
-|-----------------|-----------------------------------------------------|
-| OIDC_PROVIDER   | URL of the OIDC provider                           |
-| OIDC_CLIENT_ID  | The client ID                                       |
-| OIDC_CLIENT_SECRET | The client secret                               |
-| GRPC_ENDPOINT   | The endpoint of the deployed application            |
-
-### Creating the Secret
-
-To create the secret, you can use the following `kubectl` command:
-
-```sh
-kubectl create -n <namespace> secret generic feedback-fusion-integration-test \
-  --from-literal=OIDC_PROVIDER=<oidc_provider_url> \
-  --from-literal=OIDC_CLIENT_ID=<client_id> \
-  --from-literal=OIDC_CLIENT_SECRET=<client_secret> \
-  --from-literal=GRPC_ENDPOINT=<grpc_endpoint>
-```
-
-### Run the tests 
-
-```sh 
-helm test -n <namespace> <release>
-```
-
-### On finish
-
-You should now reset your database as the integration test does not delete everything it created.