New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate split_checkout
feature by default
#10693
Activate split_checkout
feature by default
#10693
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, very simple.
Long-term, I was wondering if we should expand our current list of features with two more lists. We could have:
- current features with descriptions
- active features
- retired features
Then we always enable the active features and delete the retired features. Devs can then just move those feature names around. But the big downside would be that we enable the feature whenever the server is restarted even if we deactivated it again because there was a problem.
Another idea would be to have a rake task which can be triggered with ofn-install for all instances. That seems much better to me to control the timing or repeat it if necessary. Anyway, migrations are an easy way as well and don't require any additional work for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't you be updating this file as well https://github.com/openfoodfoundation/openfoodnetwork/blob/master/lib/open_food_network/feature_toggle.rb ?
You mean, by changing the description of the feature for example? Or anything else? |
I meant by moving it to RETIRED_FEATURE, but I realize now that I am jumping the gun, ignore me. |
Hi @jibees, After staging the PR the flipper is activated automatically again and I see the split checkout: I can still disable the feature manually and use the legacy checkout. I have also tried deleting the flipper and re-staged the PR. This still showed the legacy checkout: So I switched from UK to AU and immediately deleted the flipper (while split checkout was active). This brought back the legacy checkout: Then I staged the PR and this brought split checkout back and activated automatically. I think this is ready to go but leaving for you to decide and merge. |
Yes, because migration has already been executed: that's why when you switch to AU (instead of UK) the migration can run, and then the split_checkout feature is activated. |
What? Why?
What should we test?
/admin/feature-toggle/features
deactivate or deletesplit_checkout
featureRelease notes
Changelog Category: User facing changes
The title of the pull request will be included in the release notes.
Dependencies
Documentation updates