The native installation should pin MFE versions

[arbrandes]

Description

Recently, a commit that likely introduced a backward-incompatible change (if not a bonafide bug!) to the Gradebook MFE and Lilac.master. Even if the Gradebook is not officially supported for Lilac by the BTR group, we need a way to avoid such upstream changes from breaking the other ones.

A suggested solution is to add the following to the pre-existing MFE vars on openedx_native.yml:

MFE_DEPLOY_VERSION: {{ OPENEDX_RELEASE }}

Acceptance criteria

• A generic solution (not necessarily the suggested one) is found for all MFEs
• It is tested to work with all group-supported MFEs (Account, Payment, and Ecommerce) by making sure that after a native installation the proper version is checked out)
• A PR to master is merged
• A PR to lilac.master is merged

Estimated effort

2 hours of a developer experienced with the native installation

Bounties

N/A

[BbrSofiane]

@arbrandes What were the steps to reproduce this issue?

I've run a native installation and all the MFEs are checked out with the correct branch (open-release/lilac.master).

Looking at edx/configuration/install/native.sh, MFE_DEPLOY_VERSION is set by the install script.

[arbrandes]

@BbrSofiane, excellent catch. This issue was reported to me by the Opencraft team when deploying via Ocim, and I neglected to check native.sh. I guess we can close this, then. :)