-
Notifications
You must be signed in to change notification settings - Fork 1
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
[CAI-63] Chatbot: create vector index from pipeline #1159
base: main
Are you sure you want to change the base?
Conversation
|
This pull request is stale because it has been open for 14 days with no activity. If the pull request is still valid, please update it within 21 days to keep it open or merge it, otherwise it will be closed automatically. |
his whole part of the pipeline will be run on a self hosted runner on AWS CodeBuild. CodeBuild has its own role that can be used to contact AWS services For this reason, it is not necessary to set IAM credentials/roles Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
This makes the entire step to run on the self-hosted runner in AWS. Also, this takes into account the target environment. Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Co-authored-by: christian-calabrese <[email protected]>
Branch is not up to date with base branch@batdevis it seems this Pull Request is not updated with base branch. |
Jira Pull Request LinkThis Pull Request refers to the following Jira issue CAI-63 |
List of Changes
Addess "chatbot" action to deploy workflows.
Motivation and Context
We need to recreate LLamaindex Vector Index on Redis every time the documentation is recreated.
How Has This Been Tested?
I can't test it in local development.