What is the impact of the MFE image not being pre-built?

[kdmccormick]

Context

Read about the problem: https://discuss.overhang.io/t/why-is-the-mfe-image-not-pre-built/2260

Check out this Frontend WG milestone "MFE Config 2.0", which might solve the problem: https://github.com/openedx/frontend-wg/milestone/2

Acceptance

Answer these questions:

• Would "MFE Config 2.0" as described allow the mfe image to be pre-built?
• How much of a pain point is the lack of a pre-built mfe image to k8s/local usage? How about for dev usage?
  • If it's small:
    • Is there a workaround we can document for now?
  • If it's significant:
    • Is there a medium-term solution we could pursue, like adjusting how the remote-image hook works?
    • Or, could we expedite work with Frontend WG to expedite MFE Config 2.0?

Write up issue(s) for follow-up if necessary.

[kdmccormick]

@regisb Here's one more. I'm going to consider this one "Groomed" as it's just a bunch of questions to answer, so grooming it seems redundant.

[kdmccormick]

• Would "MFE Config 2.0" as described allow the mfe image to be pre-built?
  • Yes, it would. Being able to dynamically load configuration without rebuilding would completely solve the problem.
• How much of a pain point is the lack of a pre-built mfe image to k8s/local usage? How about for dev usage?
  • It's annoying but not a showstopper. The pain points are:
    • tutor images pull all fails when the mfe plugin is enabled
    • tutor ... quickstart is slower, as it must build the MFE image instead of downloading it.
    • Is there a workaround we can document for now?
      • We could tell people to disable the MFE before running tutor images pull all
    • Is there a medium-term solution we could pursue, like adjusting how the remote-image hook works?
      • Once the v1 plugin API merges, we could rewrite the tutor-mfe plugin to use the v1 API, and in doing so we could implement this image-pulling workaround.
    • Or, could we expedite work with Frontend WG to expedite MFE Config 2.0?
      • I will keep nudging the WG about Config 2.0, but it's not going to be done before the conference at the very least.

I created #59 to track the plugin rewrite.

I haven't made a ticket for the docs update, since I'm not sure it's worth it.