Add a .env file in the root folder with the following content:
DATASPOT_EMAIL_RECEIVERS_TECHNICAL_ONLY=["petra.muster@bs.ch", "peter.muster@bs.ch"]
DATASPOT_EMAIL_RECEIVERS=["petra.muster@bs.ch", "peter.muster@bs.ch"]
DATASPOT_EMAIL_SERVER=
DATASPOT_EMAIL_SENDER=For machine-to-machine authentication using Azure AD/Entra ID:
# Azure AD/Entra ID configuration
DATASPOT_TENANT_ID=your-azure-tenant-id
DATASPOT_CLIENT_ID=your-entra-app-client-id
DATASPOT_CLIENT_SECRET=your-entra-app-client-secret
DATASPOT_EXPOSED_CLIENT_ID=5d25a...612
# Dataspot service user access key
DATASPOT_SERVICE_USER_ACCESS_KEY=your-service-user-access-keyThe following environment variables can be deleted, if they still exist. They are from a legacy system.
DATASPOT_EDITOR_USERNAME
DATASPOT_EDITOR_PASSWORD
DATASPOT_ADMIN_USERNAME
DATASPOT_ADMIN_PASSWORD
DATASPOT_CLIENT_ID
DATASPOT_AUTHENTICATION_TOKEN_URL
DATASPOT_API_BASE_URLNote: The authentication system has been updated to use M2M authentication. The legacy username/password authentication may be deprecated in the future.
The following gif shows everything needed to create a new post, and link the correct person. Note that we don't actually need to create the person or user, as this happens daily automatically.

When integrating a dev into prod, first we need to clone the dev into an int database.
Then:
- Export DNK from
devas xlsx and import it again (dry run is enough). - If we don't fix warnings or errors that occur, then they will appear later again.
- Integrate yaml from
devintoint - Run job "Regelverletzungen prüfen"
- Export DNK as xlsx and import it again (dry run is enough)
- Export and reimport other models that might be affected aswell
- Merge
devintomainand deletedevbranch
If everything worked without errors, we can apply the int yaml into the prod yaml and reapply the changes made to the int to the prod.
After that, delete the dev branch on github, in dataspot, and also its corresponding Annotations.yaml. Also delete the int environment in dataspot.