Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

Sync Discord User with Ombi User #56

Open
v0idp opened this issue Jan 18, 2020 · 9 comments
Open

Sync Discord User with Ombi User #56

v0idp opened this issue Jan 18, 2020 · 9 comments
Assignees
Labels
Feature Request Requesting a new feature Medium Priority This should be done but not so fast there cowboy!

Comments

@v0idp
Copy link
Owner

v0idp commented Jan 18, 2020

Sync discord user with ombi user. Maybe create new user for each discord user who wants to sync up ?

@v0idp v0idp added the Feature Request Requesting a new feature label Jan 18, 2020
@v0idp
Copy link
Owner Author

v0idp commented Jan 20, 2020

Something to keep in mind for this feature:
https://github.com/tidusjar/Ombi/wiki/Discord-Notification-Settings

Maybe we could sync users by adding their discord tag to the user preferences. We need find a way to sync discord with ombi users.

@v0idp v0idp added the Medium Priority This should be done but not so fast there cowboy! label Jan 21, 2020
@v0idp
Copy link
Owner Author

v0idp commented Jan 22, 2020

Don't forget this:

return this.requestContent('tv', { 'tvDbId': tvdbid, "requestAll": true}, name);

@Malcolmest
Copy link

I'm basically just a power user with little code experience but have you tried contacting Tidusjar, the ombi dev, for assistance? This feature would be so great!

@v0idp
Copy link
Owner Author

v0idp commented Feb 16, 2020

I know already how to do this but I'm currently working on another high priority bugs which need to be fixed first.

@robbiet480
Copy link

Took a quick look at this. Part of the problem is that we currently are requesting in Ombi as the API key user, not as the actual Discord user. So the first change needed will be to either let Ombi accept a Ombi user ID when making a request or run a PUT request after the request POST where we set the requesting user. Then Discord notifications will work properly.

@v0idp
Copy link
Owner Author

v0idp commented May 19, 2020

Took a quick look at this. Part of the problem is that we currently are requesting in Ombi as the API key user, not as the actual Discord user. So the first change needed will be to either let Ombi accept a Ombi user ID when making a request or run a PUT request after the request POST where we set the requesting user. Then Discord notifications will work properly.

you can request as a user by changing the UserName attribute in the header when requesting content. we would need to add a sync ombi command so the user id gets linked to the plex account. we will need to do some oauth2 trickery probably to get it properly synced and then it should work.

@Alpha5k
Copy link
Contributor

Alpha5k commented May 19, 2020

Actually that's not necessary. Ombi has a "Discord" field for each user under notifications. If you add their ID it pings the user with the Discord webhook. All we need to do is check if the user who made the request has an account with that ID. Fortunately Ombi has an endpoint that returns this data. I'll make a PR for this shortly.

@AzzieDev
Copy link

AzzieDev commented Jun 8, 2020

So this would allow us to say something like [RequesterName} in the Ombi notification and it would retrieve the discord name#number that can mention them?

@robbiet480
Copy link

robbiet480 commented Jul 14, 2020

@Alpha5k Get anywhere with that PR ever? If not, I can take a swing at it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature Request Requesting a new feature Medium Priority This should be done but not so fast there cowboy!
Projects
None yet
Development

No branches or pull requests

5 participants