down migration on gcp llink dev db and then import neon data in
get rid of the workaround for prepared statements
deploy orion and particle processor worker dev using this gcp db
create prod database for llink, add to cluster secrets
create orion and worker deployment in prod (research site is in prod cluster, so needs orion there). hook this orion up to the llink database in prod gcp project
research-site: create client for orion, and use it for adding to waitlist on form input. remove dep on aero and everything else
We currently have our `research-site` logging waitlist entries to `helios`, and not `orion` which would insert it into our llink postgres database.
- [x] add waitlist service to orion
- [x] send email notifications to `[email protected]` from waitlist service
- [x] down migration on gcp llink dev db and then import neon data in
- [x] get rid of the workaround for prepared statements
- [x] deploy orion and particle processor worker dev using this gcp db
- [x] create prod database for llink, add to cluster secrets
- [x] create orion and worker deployment in prod (research site is in prod cluster, so needs orion there). hook this orion up to the llink database in prod gcp project
- [x] research-site: create client for orion, and use it for adding to waitlist on form input. remove dep on aero and everything else
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We currently have our
research-sitelogging waitlist entries tohelios, and notorionwhich would insert it into our llink postgres database.[email protected]from waitlist service