Automate cloud functions deployment

[marvinmarnold]

Notes

There are three servers:

• NextJS frontend: Vercel, autodeployments working
• Postgres DB for saving queries: Supabase, autodeployments not necessary yet
• Endpoint for LLM computation: Google Cloud Functions, autodeployment removed because wasn't working

Only the cloud functions are in scope. Additional notes:

• There are a bunch of unused functions. Those were for tests and can be ignored.
• Currently using 4GB of memory for deployments, eg:

gcloud functions deploy getanswer \
    --gen2 \
    --runtime=python310 \
    --memory=4GB \
    --region=us-east1 \
    --source=packages/googlecloud/functions/getanswer \
    --entry-point=getanswer \
    --trigger-http \
    --allow-unauthenticated \
    --set-env-vars OPENAI_API_KEY=${{ secrets.OPENAI_API_KEY }}

• Not sure why deployments were failing before. One known issue is adding unnecessary quotes to OPENAI_API_KEY. Typically failed deployments manifest with CORS errors when the web client attempts to invoke the function.
• OPENAI_API_KEY env var is already stored in GIthub.

Acceptance criteria

• Deploys to getanswer when PR merged into prod branch.
• prod branch created. Write protections added to Github to prevent direct pushes.
• Deploys to getanswer-staging when PR merged into main branch.
• Bonus: Anything easy we can do to have a custom ephemeral function for each PR? In another project we are using git hashes, but it requires a nontrivial amount of code.

[nikkag]

Reactivated the workflow for staging: On a push to main, the code will deploy to getanswer-staging
3974df9

[nikkag]

Build failed
Will investigate more later on to see what went wrong. For now I redeployed the staging function using the zip.

[nikkag]

Moving cache files out of the repo and using dvc to manage them seems to have fixed the issue!

• PR Fix main deploy #48 for updating staging workflow + adding production workflow.
• prod branch has been created and protections added.

Will give ephemeral functions for PRs more thought.

[marvinmarnold]

Awesome. I'm not 100% sure but I think those large files will perpetually cause bloat in git history and increase the download size to clone. Created an issue to deal with that eventually.