This PR modifies our existing site creation form to utilise the new email login flow instead. Currently, our site creation form creates a new website, but does not assign site members to the new site - thus our creation flow currently creates an Amplify site that is accessed via Github login, with access manually granted to users via Github. This PR changes the creation flow to associate an existing isomer user to the specified site, or create a new isomer user using the specified email if no such user exists. A new form has also been created for both staging and production (staging form link). Note that the person filling in the form is still specified as the owner of the form.
Env var changes before merging:
Modify SITE_CREATE_FORM_KEY on production - we're using a new site create form (v3) just to be safe, so the form key needs to be swapped out to the new secret key
This PR modifies our existing site creation form to utilise the new email login flow instead. Currently, our site creation form creates a new website, but does not assign site members to the new site - thus our creation flow currently creates an Amplify site that is accessed via Github login, with access manually granted to users via Github. This PR changes the creation flow to associate an existing isomer user to the specified site, or create a new isomer user using the specified email if no such user exists. A new form has also been created for both staging and production (staging form link). Note that the person filling in the form is still specified as the owner of the form.
Env var changes before merging:
SITE_CREATE_FORM_KEYon production - we're using a new site create form (v3) just to be safe, so the form key needs to be swapped out to the new secret key