Add a .env file in the root folder with the following content:
DATASPOT_EMAIL_RECEIVERS=["petra.muster@bs.ch", "peter.muster@bs.ch]
DATASPOT_EMAIL_SERVER=
DATASPOT_EMAIL_SENDER=
DATASPOT_EDITOR_USERNAME=
DATASPOT_EDITOR_PASSWORD=
DATASPOT_ADMIN_USERNAME=
DATASPOT_ADMIN_PASSWORD=
DATASPOT_CLIENT_ID=
DATASPOT_AUTHENTICATION_TOKEN_URL=https://login.microsoftonline.com/organizations/oauth2/v2.0/token
DATASPOT_API_BASE_URL=https://www.myserver.comWhen 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.
Not explicitely defined, this is written here just so that I know what I used before. You can use whatever you want.
- dev: 167a3e
- int: ff0000