made readme reflect new reduced scope

README.md

@@ -1,3 +1,8 @@
 # DailyStakeholderReport-Pipeline
 
-Scripts I use to help gather data and publish my daily stakeholder report. 
+This repo is very similiar to my other markdown/PDF micro servcies.
+
+It...
+
+- Renders a yaml template using values passed in by the calling microservice.
+- Uses pandoc with the rendered yaml template to create a PDF.

build/build-stakeholder-output-server.sh

@@ -0,0 +1,20 @@
+#!/bin/bash
+
+set -euo pipefail
+
+# Expand variables into rendered YAML files. These will be used by pandoc to format the output artifacts
+$MO_PATH $YamlInputTemplateFileStakeholderOutput > $BUILDYAML_STAKEHOLDER_OUTPUT
+
+echo "Creating stakeholder report..."
+
+cd "$(dirname $StakeholderOutputMarkdownInputFile)"
+
+pandoc \
+"$StakeholderOutputMarkdownOutputFile" \
+--template $PANDOC_TEMPLATE \
+--metadata-file="$BUILDYAML_STAKEHOLDER_OUTPUT" \
+--from markdown \
+--to=pdf \
+--output $StakeholderOutputPDFOutputFile
+
+cd -

create-and-publish-dsr.sh

@@ -1,152 +0,0 @@
-#!/bin/bash
-
-secrets_manager()
-{
-
-echo "Obtaining discourse api key..."
-
-bw logout
-
-####################################
-## Step 0: Set to use tsys server
-####################################
-bw config server https://pwvault.turnsys.com
-
-####################################
-## Step 1: login to bitwarden
-####################################
-
-# From: https://bitwarden.com/help/cli/#using-an-api-key
-
-### Set apikey environment varaible
-
-source D:/tsys/secrets/bitwarden/data/apikey-bitwarden-reachableceo
-
-### Login to vault using apikey...
-
-bw login --apikey $BW_CLIENTID $BW_CLIENTSECRET
-
-### Step 1.1: unlock / save session id 
-
-export BW_SESSION="$(bw unlock --passwordenv TSYS_BW_PASSWORD_REACHABLECEO --raw)"
-
-### Step 2: retrive a value into an environment variable
-
-export DISCOURSE_APIKEY="$(bw get password APIKEY-discourse)"
-
-}
-
-generate_dsr()
-{
-
-echo "Creating PDF of DSR from markdown input via pandoc..."
-
-INPUT_FILE="./DSR-$(date +%m-%d-%Y).md"
-OUTPUT_FILE="./DSR-$(date +%m-%d-%Y).pdf"
-METADATA_FILE="daily-stakeholder-report.yml"
-TEMPLATE="eisvogel"
-
-pandoc \
-$INPUT_FILE \
---template $TEMPLATE \
---metadata-file=$METADATA_FILE \
---from markdown \
---to=pdf \
---output $OUTPUT_FILE
-}
-
-post_dsr()
-
-{
-echo "Posting DSR..."
-
-#!/bin/bash
-
-# Replace these with your Discourse instance details
-DISCOURSE_URL="https://community.turnsys.com"  # e.g., https://forum.example.com
-API_KEY="$DISCOURSE_APIKEY" # Your API key
-API_USERNAME="reachableceo" # API username or admin account
-
-# The category ID to post to (update to match your forum's categories)
-CATEGORY_ID=61
-
-# The title for the post (generated here; customize as needed)
-TITLE="Daily Stakeholder Report - $(date +'%m-%d-%Y')"
-
-# The content of the post
-CONTENT="Please see the attached PDF for today's report."
-
-# The file to upload (from the second argument or auto-generated based on date)
-FILE_PATH="./DSR-"$(date +%m-%d-%Y)".pdf"
-
-# Check if the file exists
-if [ ! -f "$FILE_PATH" ]; then
-  echo "File not found: $FILE_PATH"
-  exit 1
-fi
-
-# Upload the file
-echo "Uploading file..."
-upload_response=$(curl -s -X POST "$DISCOURSE_URL/uploads.json" \
-  -H "Content-Type: multipart/form-data" \
-  -H "Api-Key: $API_KEY" \
-  -H "Api-Username: $API_USERNAME" \
-  -F "file=@$FILE_PATH;type=application/pdf" \
-  -F "type=composer")
-
-echo "Upload Response: $upload_response"
-
-# Extract the short_url from the response
-short_url=$(echo "$upload_response" | /mingw64/bin/jq -r '.short_url')
-
-# Check if the short_url was returned
-if [ "$short_url" == "null" ]; then
-  echo "Failed to extract short_url. Response:"
-  echo "$upload_response"
-  exit 1
-fi
-
-echo "File uploaded successfully. Short URL: $short_url"
-
-# Append the file link to the post content (Markdown format)
-CONTENT="$CONTENT\n\n[Download the PDF]($short_url)"
-
-# Create the new topic
-echo "Creating new topic..."
-post_response=$(curl -s -X POST "$DISCOURSE_URL/posts.json" \
-  -H "Content-Type: application/json" \
-  -H "Api-Key: $API_KEY" \
-  -H "Api-Username: $API_USERNAME" \
-  -d @- <<EOF
-{
-  "title": "$TITLE",
-  "raw": "$CONTENT",
-  "category": $CATEGORY_ID
-}
-EOF
-)
-
-echo "Post Response: $post_response"
-
-# Check if the post creation was successful
-if echo "$post_response" | grep -q '"id":'; then
-  echo "Post created successfully!"
-else
-  echo "Failed to create post. Response:"
-  echo "$post_response"
-  exit 1
-fi
-
-
-
-
-}
-
-#Create PDF from joplin exported markdown
-generate_dsr
-
-#Get discourse api key
-secrets_manager 
-
-#Create a new topic and upload/attach PDF to the topic
-post_dsr

dsr-datagather-gitea-activity.sh

@@ -1,83 +0,0 @@
-#!/bin/bash
-
-# Script to query Gitea API for a user's activity on a specific date
-
-########################################################################################################
-#Obtain gitea api key from bitwarden
-########################################################################################################
-
-####################################
-## Step 0: Set to use tsys server
-####################################
-bw logout
-
-echo "Setting cli to use tsys bitwarden server..."
-bw config server https://pwvault.turnsys.com
-
-####################################
-## Step 1: login to bitwarden
-####################################
-
-# From: https://bitwarden.com/help/cli/#using-an-api-key
-
-### Set apikey environment varaible
-
-echo "Sourcing clientid/apikey data..."
-source D:/tsys/secrets/bitwarden/data/apikey-bitwarden-reachableceo
-
-### Login to vault using apikey...
-
-echo "Logging in..."
-bw login --apikey $BW_CLIENTID $BW_CLIENTSECRET
-
-### Step 1.1: unlock / save session id 
-
-echo "Unlocking..."
-export BW_SESSION="$(bw unlock --passwordenv TSYS_BW_PASSWORD_REACHABLECEO --raw)"
-
-
-### Step 2: retrive a value into an environment variable
-
-export GITEA_APIKEY="$(bw get password APIKEY-Gitea)"
-
-########################################################################################################
-# Accrss gitea data
-########################################################################################################
-
-# Script to query Gitea API for a user's activity on a specific date
-
-# Usage: ./get_gitea_user_activity.sh <username> <date> [GITEA_URL] [TOKEN]
-
-# Set username, date, and default Gitea URL
-USERNAME="${1:-reachableceo}"                    # Default to "reachableceo" if not provided
-DATE="${2:-$(date +%Y-%m-%d)}"                   # Default to today's date if not provided
-GITEA_URL="${3:-https://git.knownelement.com}"   # Default Gitea URL if not provided
-TOKEN="${GITEA_APIKEY}"                      # Use APIKEY-GItea or passed argument
-
-# API Endpoint for user activities
-API_ENDPOINT="$GITEA_URL/api/v1/users/$USERNAME/timeline"
-
-# Make the API call
-if [ -n "$TOKEN" ]; then
-  # If token is provided, use it in the Authorization header
-  RESPONSE=$(curl -s -H "Authorization: token $TOKEN" "$API_ENDPOINT")
-else
-  # If no token is provided, make an unauthenticated request
-  RESPONSE=$(curl -s "$API_ENDPOINT")
-fi
-
-# Check for API errors
-if [[ "$RESPONSE" == "Not found" || -z "$RESPONSE" ]]; then
-  echo "Error: User '$USERNAME' not found, or endpoint is incorrect."
-  exit 1
-fi
-
-# Validate JSON response
-if ! echo "$RESPONSE" | jq empty >/dev/null 2>&1; then
-  echo "Error: Invalid JSON response from Gitea API."
-  echo "Response: $RESPONSE"
-  exit 1
-fi
-
-# Filter the activity by date using jq
-echo "$RESPONSE" | jq --arg date "$DATE" '[.[] | select(.created_at | startswith($date))]'