Skip to content

refactor!: Using Waffle flag to enable Account MFE globally. - #27623

Merged
robrap merged 1 commit into
openedx:open-release/lilac.masterfrom
eduNEXT:eric/enable_account_mfe_globally_backport
May 18, 2021
Merged

refactor!: Using Waffle flag to enable Account MFE globally.#27623
robrap merged 1 commit into
openedx:open-release/lilac.masterfrom
eduNEXT:eric/enable_account_mfe_globally_backport

Conversation

@ericfab179

Copy link
Copy Markdown
Contributor

Backport of #27518

Related BTR issue openedx/wg-build-test-release#27

This commit refactors the way the Account MFE is activated in the
platform. The main objective is to control the global
activation/deactivation of the MFE through the
account.redirect_to_microfrontend waffle flag and use the Site
Configurations to control MFE activation/deactivation with per-site
granularity. Notice that the Site Configuration object will have
precedence over the waffle flag value.

Since the classic Account Django view will be most likely supported
during Lilac, the expiration of this temporary waffle flag was
extended till the end of 2021

With this commit:

- There's no need to create a Site Configuration object to get the MFE
activated. Setting the waffle flag to True is enough.
- It helps multisite installations to better handling granular
per-site activation/deactivation.

BREAKING CHANGE:

For operators of multisite installations, the activation of the waffle
flag will now activate the MFE for all sites, unless explicitly
disabled on a per-site basis.

Otherwise, this is a backwards-compatible change, since the MFE will
remain activated for installations where this is already enabled.
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @ericfab179! I've created OSPR-5779 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket:

  • supporting documentation
  • Open edX discussion forum threads
  • timeline information ("this must be merged by XX date", and why that is)
  • partner information ("this is a course on edx.org")
  • any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

@openedx-webhooks openedx-webhooks added needs triage open-source-contribution PR author is not from Axim or 2U labels May 13, 2021
@jfavellar90

Copy link
Copy Markdown
Contributor

@nedbat do we need a PR for this backport? or you can apply the cherry-pick?

@BbrSofiane

Copy link
Copy Markdown
Contributor

@robrap since #27518 has been approved, can you also approve and merge this PR? This would allow us to create the first release candidate for lillac.

cc: @felipemontoya @pdpinch

@robrap
robrap merged commit 4de22fa into openedx:open-release/lilac.master May 18, 2021
@openedx-webhooks

Copy link
Copy Markdown

@ericfab179 🎉 Your pull request was merged!

Please take a moment to answer a two question survey so we can improve your experience in the future.

sambapete added a commit to EDUlib/edx-platform that referenced this pull request May 19, 2021
…_global…

…ly_backport

refactor!: Using Waffle flag to enable Account MFE globally.
@natabene

Copy link
Copy Markdown
Contributor

@ericfab179 @robrap Thank you both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged open-source-contribution PR author is not from Axim or 2U

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants