-
Notifications
You must be signed in to change notification settings - Fork 6
Feature 2868/pull slack kudos in #2876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…s, persist automated kudos.
…tent for json when sending it to the poster.
…if the server is not running.
| @Inject | ||
| private SlackKudosCreator slackKudosCreator; | ||
|
|
||
| @Scheduled(fixedDelay = "10m") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we can count on this because sometimes we scale down completely...and we will end up with multiple channel readers when the app is busy as well. We can end up with up to 10 instances running currently, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mkimberlin I just checked in a change to remove the scheduled task and tie it to the CheckServicesController.
…s a kudos from public to private or deletes a public kudos.
This adds a scheduled task to read slack messages from a configured channel and import user messages as Check-Ins Kudos upon verification with the poster of the slack message.
slackservice directory.CurrentUserServicesImpl.hasPermissionto return false if there is no current user.PulseResponseControllerSLACK_KUDOS_CHANNEL_IDvalue.C0814P2PEV7This will need to be deployed to finish testing.
Also, once this is deployed to production, we will need to add the following scopes to the Check-Ins Integration.
channels:historychat:writegroups:historyim:write