Skip to content

Migration master slave installation

Jump to bottom
Edwin Woudt edited this page Feb 1, 2020 · 4 revisions

Introduction

Note: if you are installing bunq2IFTTT for the first time, please ignore this page and go to the Home page.

In a previous version of bunq2IFTTT, a more complicated security model was used because the bunq API did not allow real time notifications with OAuth. Since that has been changed, bunq2IFTTT has been updated and simplified. This page describes how to migrate from the old to the new situation.

Note: before you start, first Upgrade your installation to the newest version.

Step 1: delete the API key used for your slave

Since this is no longer needed, you can delete the API key in the bunq app:

  1. First open the bunq app, and go to your profile
  2. Click on the Security & Settings option
  3. On the Security & Settings page, select the Developers option
  4. On the Developers page, select the API keys option
  5. Click on the bunq2IFTTT key and click on Delete

Step 2: update your master installation

Update your master installation by downloading the newest version and using the following commands:

gcloud app deploy --project your-project-id app
gcloud app deploy --project your-project-id app/cron.yaml

(Of course, replace 'your-project-id' with the appropriate project id you chose during installation)

Step 3: reconfigure bunq2IFTTT

Next you need to setup bunq2IFTTT again:

  1. Login to bunq2IFTTT by going to its webpage and filling in the password
  2. Enter the IFTTT service key again
  3. Start the OAuth connection workflow

For more details, see Configure bunq2IFTTT

Step 4: setup the OAuth expires trigger

This step is optional, but highly recommended as OAuth connections expire after 90 days, and you can use this trigger to give you a reminder to renew it.

See: Configure oauth expires trigger

Clone this wiki locally