itsgc / raidnight Goto Github PK

This may have to do with the fact i used sessions in requests? maybe?

Either way, when it breaks the spreadsheet becomes empty.

We want to know when the app serves a request as well as when it hits an upstream error

This might be a better fit than EB and might address part of #21

Right now, ImportJSON only retriggers if something in the cell changes, which is cumbersome.

Find a better way to refresh data

There are some <60 characters currently included

Start by implementing it in blizz_test.py and move it to application.py once refined.

This is a common pattern i have sample code for in other projects, import it here.

We don't want everybody to abuse our endpoint to poll Blizzard and use our rate limit quota, so let's make sure that the json endpoint is authenticated. Use Flask-BasicAuth as shown here: https://flask-basicauth.readthedocs.io/en/latest/

Plan is to use https://github.com/bradjasper/ImportJSON to import raw json data for the guild roster in Google sheet and use that as our UI. The guild is already accustomed to it and it's easy to slice and dice data.

Let's test if we can import data from our Elastic Beanstalk app by setting up a flask route with a basic json document as a response

Lay down the foundations to be able to poll the blizzard API in a modular way, for example by creating an api client library that the flask service will be able to consume.

I knew the code to fetch a token was simplistic, the root cause for #21 is actually that the token expires and we get a 400 back from blizz api.

Implement smart token handling that checks expiration.

• Fill character details (ilvl, name, class, role, guild note, spec)
• Use Discord as UI for raid confirmations, thumbs up / thumbs down / other emoji for tentative and get full list of who answered
• [LOWER PRIO] Track alts
• [LOWEST PRIO] Manage roles

Promoting someone in-game should be reflected in their role changing in Discord as well. Saves some manual work.

Follow https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-flask.html and put up a basic Hello World flask service in elastic beanstalk

Calendars are not exposed via API so this will be very tricky.

Possibly a mitigating strategy for #21 but a good idea either way to save on api calls

We need to use slugs for processing but we want to use friendly names within the actual response.