integrate atlas into the deployment process

[brian-smith-tcril]

in order to support the move away from having translations checked into repos (see OEP-58), we will need to update the deployment processes

while it would be possible to manually add sparse checkouts to each deployment flow, it makes more sense to utilize atlas

Relevant info/questions

• should this be integrated into frontend build somehow?
• what are all the different ways MFEs are deployed (tutor/devstack based)?
  • what needs to happen to ensure we can pull during build in all of those scenarios?

ways MFEs are deployed

• https://openedx.atlassian.net/wiki/spaces/FEDX/pages/2629829454/Micro+Frontend+MFE+Onboarding#Deploying
• tutor plugins: https://github.com/overhangio/tutor-mfe
  • example PR adding tutor plugin functionality to a MFE: Add a tutor plugin to easily run this on a devstack openedx-unsupported/frontend-app-library-authoring#50
  • adding "custom" translation to MFEs installed with tutor https://github.com/overhangio/tutor-mfe#adding-custom-translations-to-your-mfes (manually editing the json files and rebuilding)
    • do we need to support "custom" translations? when should atlas pull replace existing translation files? should we continue to use https://github.com/overhangio/tutor-mfe/blob/master/tutormfe/templates/mfe/build/mfe/i18n/i18n-merge.js ?
  • i18n part of tutor mfe dockerfile https://github.com/overhangio/tutor-mfe/blob/9b1b08f2d9e9dfa0faec54dddd9443930ca56b12/tutormfe/templates/mfe/build/mfe/Dockerfile#L16-L37
    • this relies on https://github.com/overhangio/tutor-mfe/blob/master/tutormfe/templates/mfe/build/mfe/i18n/i18n-merge.js
  • makefile is unused in MFEs, npm run build is run in the dockerfile https://github.com/overhangio/tutor-mfe/blob/9b1b08f2d9e9dfa0faec54dddd9443930ca56b12/tutormfe/templates/mfe/build/mfe/Dockerfile#L90

possible paths forward:

• edx.org
  • ?
• Tutor
  • adding atlas pull to npm run build would cause problems with the existing custom translations merge logic
  • so one possible solution there is to edit the dockerfile to pull translations during the copying i18n data step
    • this would require testing to ensure the i18n-merge.js logic still works as intended