Closed seaerchin closed 1 year ago
This PR has quite a number of infra moving parts - eg.
- formsg
- efs
- be
Could we do a quick sanity check testing on stg before release? since this is internal use using post deploy testing is also fine, thoughts?
tbh, i think the only difference between testing on staging vs not, is that the clone step takes place in a different environment (with all of the annoyances that entails); i think i'll just do post-deploy cos it's not open to public anyway.
Problem
See here
Solution
/formsg/clone-repo
.open.gov.sg
and must verify email + repo is a required field)New env vars
SITE_CLONE_FORM_KEY
: used to decrypt the form sg submissions (already added to 1PW on bothstaging
andprod
env vars; not yet added tostaging
EB yet)Notes
this was tested locally through updating the
EFS_VOL_PATH
+originUrl
(usehttps
instead ofssh
as i was facing auth issues) and found working