zinovik / bgg-top1000-bot

Telegram Bot: @bggtop1000

BGG Top 1000

This bot posts BGG Top 1000 changes to @bggtop1000 every week.

google cloud setup

create bucket:

gcloud storage buckets create gs://boardgamegeek --location=europe-central2
gcloud storage buckets update gs://boardgamegeek --versioning

create schedulers

gcloud scheduler jobs create http bgg-top1000-bot --location=europe-central2 --schedule="0 9 * * 6" --uri="https://europe-central2-zinovik-project.cloudfunctions.net/bgg-top1000-bot?channelId=@bggtop1000&isDevMode=off" --oidc-service-account-email=[e-mail] --http-method=get --oidc-token-audience="https://europe-central2-zinovik-project.cloudfunctions.net/bgg-top1000-bot" --attempt-deadline=180s

gcloud scheduler jobs create http bgg-top1000-bot-dev --location=europe-central2 --schedule="0 15 * * 5" --uri="https://europe-central2-zinovik-project.cloudfunctions.net/bgg-top1000-bot?channelId=446618160&isDevMode=on" --oidc-service-account-email=[e-mail] --http-method=get --oidc-token-audience="https://europe-central2-zinovik-project.cloudfunctions.net/bgg-top1000-bot" --attempt-deadline=180s

create service account

gcloud iam service-accounts create github-actions

add roles (Service Account User and Cloud Functions Admin) to the service account you want to use to deploy the function

gcloud projects add-iam-policy-binding zinovik-project --member="serviceAccount:[e-mail]" --role="roles/cloudfunctions.admin"

gcloud projects add-iam-policy-binding zinovik-project --member="serviceAccount:[e-mail]" --role="roles/iam.serviceAccountUser"

creating keys for service account for github-actions GOOGLE_CLOUD_SERVICE_ACCOUNT_KEY_FILE

gcloud iam service-accounts keys create key-file.json --iam-account=[e-mail]
cat key-file.json | base64

add access to secrets

gcloud projects add-iam-policy-binding zinovik-project --member="serviceAccount:[e-mail]" --role="roles/secretmanager.secretAccessor"

add secrets

printf "TELEGRAM_TOKEN" | gcloud secrets create bgg-top1000-bot-telegram-token --locations=europe-central2 --replication-policy="user-managed" --data-file=-