Closed lizlooney closed 3 years ago
The key is still going to end up in the filesystem on the flask server until, or unless, we move it on the actions runner that does the app engine deploy out of the server directory.
Why? I don't understand. It is never in the server directory. Right?
Why? I don't understand. It is never in the server directory. Right?
It's the Install Key step in the terraform.yml. That drops the key in the server directory on the runner and the terraform apply, on merge, packages up that directory for a push to the app server source storage bucket. That's what those two google_storage_bucket_object resource entries in the terraform plan are showing. The files that get zipped there are the files on the runner.
If you don't mind me pushing straight to this branch, I can make this change tomorrow.
I don't mind you pushing to this branch.
plan
Succeeded for Workspace: default
The key is still going to end up in the filesystem on the flask server until, or unless, we move it on the actions runner that does the app engine deploy out of the server directory.
Also, we need to do the same for client_secrets.json which is the authentication for the oidc integration with ftc-scoring.