OPS-3 Simulate staging

Author: ToreMerkely

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

@@ -3,11 +3,12 @@ name: Report development 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 deploy to development
+# we just simulate that we have deployed to development
 
 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

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

@@ -0,0 +1,38 @@
+name: Report staging 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 staging
+
+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-staging
+  KOSLI_API_TOKEN: "${{ secrets.KOSLI_PUBLIC_API_TOKEN }}"
+  KOSLI_CLI_VERSION: "2.11.8"
+
+jobs:
+  report-snapshot:
+    name: Report staging snapshot
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: staging-running
+
+      - 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

Makefile

@@ -0,0 +1,15 @@
+SHELL  := bash
+
+deploy_to_staging:
+	@git remote update
+	@git status --untracked-files=no | grep --silent "Your branch is up to date" || (echo "ERROR: your branch is NOT up to date with remote" && exit 1)
+	git tag staging-${TIMESTAMP}
+	git push origin staging-${TIMESTAMP} $(args)
+
+	# The rest is a little extra for simulating the staging environment.
+	@if git rev-parse staging-running >/dev/null 2>&1; then \
+		git tag -d staging-running; \
+		git push --delete origin staging-running; \
+	fi
+	git tag staging-running
+	git push origin staging-running

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=2
+counter=3