Skip to content

add update trigger for docsite embeddings #669

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.

Sign up for GitHub

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

Merged
josephjclark merged 2 commits into from
Apr 23, 2025
Merged

add update trigger for docsite embeddings #669

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f5e46b
add update trigger for docsite embeddings
hanna-paasivirta Apr 22, 2025
214b07e
add comment
hanna-paasivirta Apr 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .github/workflows/trigger-embed.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
name: Trigger Embed Service

on:
push:
branches:
- main

jobs:
trigger-embed:
runs-on: ubuntu-latest
steps:
- name: Trigger Embed Service
env: # The API keys are the same as those used by the AI Assistant. There is only one (production) database.
PINECONE_API_KEY: ${{ secrets.PINECONE_API_KEY }}
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
run: |
curl -X POST https://apollo.staging.openfn.org/services/embed_docsite \
Copy link
Collaborator

@josephjclark josephjclark Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have production and staging pinecone databases, right? We only have one?

So calling out to staging will update the shared database, and production will also get the latest versions on the next search?

Copy link
Contributor Author

@hanna-paasivirta hanna-paasivirta Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as the key that is added on GitHub for this action is the same as the key used in Apollo in the AI Assistant then it will be the same shared database. So we need to make sure we add the same one on GitHub – do you have permission to add secrets?

Copy link
Collaborator

@josephjclark josephjclark Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect. Maybe we can add a comment here because this might confuse someone later on

Keys are all sorted!

-H "Content-Type: application/json" \
-d '{
"pinecone_api_key": "${{ secrets.PINECONE_API_KEY }}",
"openai_api_key": "${{ secrets.OPENAI_API_KEY }}"
}'