Example implementation of Oauth endpoints

[jaFriend]

Created the discord oauth service following the code style.

What it currently does:

• Has endpoint that redirects to discord oauth
• Has endpoint to handle the approved oauth
  • Doesn't do much other than print user guild info
  • ACM Guild is hard-coded, will want to change that soon

Ideas:

• Created yaml file that would contain guild info such as guild id, roles, permissions for that roles
  • Idea is that when a person gets the oauth request and approve, they then will get the
    permissions based off current roles.
• Stuck on a better way to do this.

Questions:

• Should implement a json web token to hold roles throughout requests after "logging in" with discord oauth?
  • Or have the permissions directly in the json web token as we just need to verify jwt and it would be the
    correct permissions.

[github-actions]

godoc reference preview ready ✨

[sidvasu]

Hi Joseph, please reformat the code to pass all the checks (use the command make smt). Also for your question, we're thinking that the web token should hold a role. There should be just two roles, one for board members and one for everyone else. Let us know if you have any more questions.