-
Notifications
You must be signed in to change notification settings - Fork 0
Home
metrics: https://app.google.stackdriver.com/?project=santaupvote
| Item | HowTo |
|---|---|
| View logs | gcloud app logs tail -s santa-api |
We're currently doing bi-weekly backups, configured via cron.yaml. In order to see, and restore a backup go to https://console.cloud.google.com/datastore/settings?organizationId=485344983296&project=santaupvote, and then click Open Datastore Admin. There you can see a list of the backups and restore any of them
replace the sha1 with the last merged sha1
gcloud auth login
gcloud config set account [YOUR_FBN_EMAIL]
gcloud config set project santaupvote
Replacing default "auto" version:
fbn/deploy.py
With custom version:
fbn/deploy.py --version v2
NOTE: If you deploy with a custom version, you need to migrate/split clients to the new version: https://console.cloud.google.com/appengine/versions?organizationId=485344983296&project=santaupvote&serviceId=santa-api&versionssize=50
bazel clean --expunge
https://santaupvote.appspot.com/api/web/votes/query https://santaupvote.appspot.com/api/web/users/query https://santaupvote.appspot.com/api/web/alerts/APPLIST/ALL https://santaupvote.appspot.com/api/web/settings/FailsafeAdministrators
- Enable santa client auth
- Enable code in upvote (ValidateClient)
- Enable client validation in santa (ClientAuthCertificateIssuerCN: https://santa.readthedocs.io/en/latest/deployment/configuration/)
- Restrict login to upvote to FBN employees (see IAP: https://console.cloud.google.com/security/iap?orgonly=true&supportedpurview=project&project=santaupvote&organizationId=485344983296&folder). Actually did this via application settings: https://console.cloud.google.com/appengine/settings?organizationId=485344983296&project=santaupvote
- have santa use full email addresses as primary user for host
- Best Practices:
- Their "emergency" button/mode doesn't say what to does, and does not seem to work: https://github.com/google/upvote/issues/22
- Updating default client mode causes all hosts to get reset: https://github.com/google/upvote/issues/21
- Filter hosts by primary user: https://github.com/google/upvote/issues/20 (amohr implemented it on our side)
- Getting XSRF errors: https://github.com/google/upvote/issues/15
- How to work with service account: https://github.com/google/upvote/issues/16
- Prevent upvote controlling client mode: https://github.com/google/upvote/issues/11
- FBN Enhancements: https://github.com/google/upvote/issues/24
- Getting timeout errors: https://github.com/google/upvote/issues/32
sudo launchctl unload /Library/LaunchDaemons/com.google.santad.plist
Backups are done bi-weekly: https://github.com/farmersbusinessnetwork/upvote/blob/master/upvote/gae/cron.yaml#L23
To roll back go to: https://console.cloud.google.com/datastore/settings?organizationId=485344983296&project=santaupvote
You can have multiple versions deployed per deploy steps above. In order roll back a version, you would just migrate all traffic to the old version here: https://console.cloud.google.com/appengine/versions?organizationId=485344983296&project=santaupvote&serviceId=default&versionssize=50