prod env reporting (#8)

* OPS-3 Added prod reporting

* OPS-3 updated apps

Author: ToreMerkely

.github/workflows/simulate-environment-reporting-prod.yml

@@ -0,0 +1,38 @@
+name: Report prod snapshot
+
+# On a normal setup the backend and frontend built in the two build jobs would
+# deploy the two artifacts to a server, and we would have set up reporting
+# of the environment to kosli. In this example we do not have a server so
+# we just simulate that we have deployed to prod
+
+on:
+  schedule:
+    - cron: '*/5 * * * *'  # Runs every 5 minutes (smallest possible)
+  workflow_dispatch:
+
+env:
+  # kosli commands picks up org, env, trail and api-token from these environment variables
+  KOSLI_ORG: kosli-public
+  KOSLI_ENV: jira-integration-example-prod
+  KOSLI_API_TOKEN: "${{ secrets.KOSLI_PUBLIC_API_TOKEN }}"
+  KOSLI_CLI_VERSION: "2.11.8"
+
+jobs:
+  report-snapshot:
+    name: Report prod snapshot
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: running-prod
+
+      - name: Setup Kosli cli
+        uses: kosli-dev/setup-cli-action@v2
+        with:
+          version:
+            ${{ env.KOSLI_CLI_VERSION }}
+
+      - name: Report snapshot
+        run: |
+          kosli snapshot paths ${{ env.KOSLI_ENV }} \
+            --paths-file server-paths-file.yml

apps/backend/backend-content.txt

@@ -1,4 +1,4 @@
 This is just a file to test out that changes to back-end source code
 can trigger a build, reporting to Kosli and Jira
 
-counter=4
+counter=5

apps/frontend/frontend-content.txt

@@ -1,4 +1,4 @@
 This is just a file to test out that changes to front-end source code
 can trigger a build, reporting to Kosli and Jira
 
-counter=4
+counter=5