We sometimes employ feature flags to develop features that aren't fully formed at the moment of deployment. They can also be employed to roll out features in production incrementally.
Feature flags are meant to be temporary and part of a rollout plan resulting in their removal.
To create a new feature flag, we use data update scripts so that they can be made available over the entire Forem fleet, for example:
1
bundle exec rails g data_update AddAwesomeAlgorithmFeatureFlag
This will generate a script and its spec. Once done, you can add the new feature flag like this:
1 2 3 4 5 6 7
module DataUpdateScripts class AddAwesomeAlgorithmFeatureFlag def run FeatureFlag.add(:awesome_algorithm) end end end
and then start using it right away.
Once the feature flag is added, you can start using it to hide the feature behind a boolean flag:
1 2 3 4 5
if FeatureFlag.enabled?(:awesome_algorithm) # call the new code else # call the previous code end
or, for example in a view:
1 2 3 4 5
<% if FeatureFlag.enabled?(:blue_button) %> <%= render "blue_button" %> <% else %> <%= render "good_old_button" %> <% end %>
As mentioned, feature flags can be used to test a work in progress feature or to test a new approach directly in production.
To enable such a feature:
/admin/feature_flags
(it requires the tech_admin
role)Once the feature has been validated and finalized or discarded, please remember to remove its flag with a final data update script, for example:
1
bundle exec rails g data_update RemoveAwesomeAlgorithmFeatureFlag
1 2 3 4 5 6 7
module DataUpdateScripts class AwesomeAlgorithmFeatureFlag def run FeatureFlag.remove(:awesome_algorithm) end end end
This will ensure that the feature will be removed from all Forems.