Release/0.39.0

[kishore03109]

v0.39.0

• fix(GGs): hotfixes from bugs identified during testing #903
• fix: require base64 #904
• fix: use synchronous fs mkdir #902
• feat(GGs): implement moving and renaming of files and directories #896
• feat: add platform predeploy hooks #877
• Fix/ggs create images #899
• Hotfix: IS-430 / 0.38.1 #900
• Feat/siteLaunch/integrationForFinalScreens #893
• Feat/is 416 ggs rollback handler #898
• Feat/is 399 ggs create file #892
• IS-401: Write extend repo service to support delete files folders #894
• IS-398: Write retrieve images from disk and return as base 64 #890
• feat(GGs): implement update operation #889
• IS-404: Write extend repo service to get latest commit of branch #891
• 0.38.0 (dev) #886
• build(deps): bump import-in-the-middle from 1.4.1 to 1.4.2 #887

[kishore03109]

Manual tests for #877

Tests

We will need to test a few things manually:

1. If EFS is mounted successfully
2. Whether 2 instances are able to see/edit the shared files in EFS
3. If SSH configs are set correctly within .ssh/
4. Whether we are able to git clone, git pull, git push from isomerpages

Deploy Notes

Note: This PR should only be merged when we are ready to rollout GGS

Dependencies:

• We will need to create an EFS volume in the staging and prod VPCs beforehand
• We will need to set the EFS ID into the SSM parameters

New SSM parameters:

1. EFS_ID - exposed on SSM to mount to the correct EFS vol
   1. STAGING_EFS_ID
   2. PROD_EFS_ID
2. STAGING_GIT_USER_NAME
   1. STAGING_GIT_USER_EMAIL
   2. PROD_GIT_USER_NAME
   3. PROD_GIT_USER_EMAIL
3. SSH keys - exposed on SSM to be fetched at deployment time
   1. STAGING_SSH_PUBLIC_KEY
   2. STAGING_SSH_PRIVATE_KEY
   3. PROD_SSH_PUBLIC_KEY
   4. PROD_SSH_PRIVATE_KEY

New environment variables:

• EFS_VOL_PATH: This should have been already added from @dcshzj 's PRs. This should point to /efs/repos.

verified by @harishv7

[kishore03109]

Tests for #890 @alexanderleegs

Tests

• Unit tests for MediaFileService, MediaDirectoryService, RepoService should all pass

• Image from non-whitelisted, public repository should continue to be retrieved from raw.githubusercontent.com

• Image from non-whitelisted, private repository should continue to be retrieved from raw.githubusercontent.com, and then converted to base64 returned to the user

• Image from whitelisted repository (regardless of public or private) should be retrieved from the local file system, then converted to base64 returned to the user

CMS Flows - Verified

• Go to Images section and ensure the images are loading correctly from disk
• Step into nested folders and ensure images are loading fine
• Right click on images -> open in new tab -> ensure image src is in base64

Note for local testing, you need to clone the repo to disk and whitelist it first

[kishore03109]

Tests for #891 @alexanderleegs

Tests

Ensure the following test suites pass:

• src/integration/NotificationOnEditHandler.spec.ts
• src/integration/Notifications.spec.ts
• src/integration/Privatisation.spec.ts
• src/integration/Reviews.spec.ts
• src/services/db/tests/RepoService.spec.ts
• src/services/identity/tests/SitesService.spec.ts

CMS Flow - Verified:

• Visit site dashboard will trigger API call to /info endpoint
• For a whitelisted repo, this should fetch the info from local disk
• For non-whitelisted repo, this should fetch the info from GitHub