n8kim1
commented
2 months ago Lowell and I tried for 2.5 hours (so like 5 dev-hours) and we couldn't get things working, but here's a listing for posterity:
A set of stuff we did to get it to work. If Titan ever seems to break, try first re-applying these changes manually
- Cloud Pub/Sub needs the role roles/iam.serviceAccountTokenCreator granted to service account service-830784087321@gcp-sa-pubsub.iam.gserviceaccount.com on this project to create identity tokens. You can change this later. Service account Titan Agent Identity to be used by the created Eventarc trigger. This trigger needs the role roles/pubsub.publisher granted to service account service-830784087321@gs-project-accounts.iam.gserviceaccount.com to receive events via Cloud Storage.
- Enable "audit logs' for the cloud run admin api
State of things now
- None of this is terraform'd so we're working on that now
What we thought of to try later:
- In terraform, set In order to use Cloud Storage triggers in Cloud Functions (2nd gen), the Cloud Storage service agent must have the Pub/Sub Publisher (roles/pubsub.publisher) IAM role on your project. This requirement does not apply to Cloud Functions (1st gen).
- do we have to manually? shouldn't this be in terraform somehow???
- check backend logs
- try staging?
- rewrite entirely in pub/sub way?
- which service ?? siarnaq or titan?
- is mitbattlecode-production-secure multiregion on accident?
lowtorola
Titan seems to not be working, and thus we cannot download resumes in the frontend2. Need to fix in order to launch, hence this falls under the alpha milestone.
Work on this issue fixes #627 as well :rocket: