feat: Added slack chat integration.

[osala-eng]

Description

Slack chat bot integration

Implements #227

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactor and code improvement (non-breaking change which improves code quality and/or performance)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation
• Tests
• Other chores such as maintenance

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration by modifying the list below.

• Test A
• Test B
• Test C

Test Configuration:

Please describe the test setup. List them below as bullet points.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings
• The commit message follows the convention of this project

[osala-eng]

@janaka I've setup slack chat bot. you can review this and tell me what you think.

I've also added the sample chat bot to the Docq.AI's slack work space you can try that out aswell.

[janaka]

Great. I'll take a look.

[janaka]

How do I do RAG? Or you waiting for the updated Web API live?

[osala-eng]

How do I do RAG? Or you waiting for the updated Web API live?

This just implements chat comletion as described in #227, once we get this approved i'll use it to implement Retrival in #228

[janaka]

great, I'll take a look at the code this weekend.

I shipped the new Web API btw.

[janaka]

Looks like the whole integration is webhooks based?

This code should be part of the API I think. It also should be designed as a general webhook handler ideally.

[janaka]

@osala-eng you see my comment about taking a look at Nango.dev as an alternative approach? I created an account in their SaaS and sent you an invite. If we go down this path will have to self-host though. This approach would definitely allow us to have a more general API our end.

[osala-eng]

Okay, let me check it out and get back to you.

…

On Tue, 12 Mar 2024, 11:16 Janaka Abeywardhana, ***@***.***> wrote: @osala-eng <https://github.com/osala-eng> you see my comment about taking a look at Nango.dev as an alternative approach? I created an account in their SaaS and sent you an invite. If we go down this path will have to self-host though. — Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APPLBJ3A7C6DQCFXHPA2K3DYX22VNAVCNFSM6AAAAABENPVKL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGAYDQNRTHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[janaka]

See comments. Please respond inline.

I've not paid attention to the integrations setting / install stuff because it seems you are still working on the changes we discussed, moving those to the Admin Section.

[osala-eng]

@janaka I've updated the changes as requested and implemented end to end slack chat with docq bot using RAG.

[janaka]

Great. Will take a look tomorrow.

[janaka]

@osala-eng sorry, I merged the Llama Index update last night. Can you rebase and check all works. Mainly with the bits that bit the Web API

[osala-eng]

@osala-eng sorry, I merged the Llama Index update last night. Can you rebase and check all works. Mainly with the bits that bit the Web API

Okay, let me rebase and test this.

[janaka]

great - do you have one or two tests for any of the new functionality build for Slack and Chrome. Would be handy to know there's something.

…

On Sun, 24 Mar 2024 at 16:31, Jashon Osala ***@***.***> wrote: @osala-eng <https://github.com/osala-eng> sorry, I merged the Llama Index update last night. Can you rebase and check all works. Mainly with the bits that bit the Web API Okay, let me rebase and test this. — Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMUQYUMGEMXMN3SJWLRRTYZ35WVAVCNFSM6AAAAABENPVKL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWHA3DCOJXGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[osala-eng]

@osala-eng I pushed a bunch of refactors. Any chance you can do a little quick test.

Okay let me do a quick test and get back to you.

[osala-eng]

This dosent work fully as some of the functionality has been disabled.

[osala-eng]

@janaka This is now ready.

[janaka]

@osala-eng did you write down anything / ref a link on how the values for the following were generated?

SLACK_CLIENT_ID
SLACK_CLIENT_SECRET
SLACK_SIGNING_SECRET

[janaka]

@osala-eng did you write down anything / ref a link on how the values for the following were generated?

SLACK_CLIENT_ID SLACK_CLIENT_SECRET SLACK_SIGNING_SECRET

@osala-eng I just remembered about the other repo with the manifest file which answer my original question sufficiently.

New related question about the env var names. You went with the SDK built-in names rather than our usual pattern of prefixing with "DOCQ_". Was that intentional for reasons like it's the only way to use the SDK? I wanted to check before refactoring to save myself some pain :)

[osala-eng]

@osala-eng did you write down anything / ref a link on how the values for the following were generated?
SLACK_CLIENT_ID SLACK_CLIENT_SECRET SLACK_SIGNING_SECRET

@osala-eng I just remembered about the other repo with the manifest file which answer my original question sufficiently.

New related question about the env var names. You went with the SDK built-in names rather than our usual pattern of prefixing with "DOCQ_". Was that intentional for reasons like it's the only way to use the SDK? I wanted to check before refactoring to save myself some pain :)

Yes, you can customize the env var names, then pass them explicitly to both App and SlackOauthFlow classes when instantiating them in the slack_application.py module. By default, slack_sdk looks for the names provided in their documentation.