Context: when in development, enabling feature flags in Travis builds of blip is best done by specifying branches specifically. However, once we go to production with the feature, we likely want that enabled for all branches so that all of our non-production remote builds will have them enabled by default without needing their branches explicitly specified.
This PR allows setting, for instance, a generic RX_ENABLED env var in Travis which can be applied to all branches as a fallback for branches not listed in the RX_ENABLED_BRANCHES variable.
If not set in Travis, the default value in our artifact.sh deployment script will be false, so it will not be accidentally deployed to production. When the time comes to deploy to production, we'll be able to simply set the RX_ENABLED var in the Travis settings to true for "All Branches" and we're good to go.
I think this pattern will be flexible enough to suit our current needs and future feature flags as they come up.
Context: when in development, enabling feature flags in Travis builds of
blipis best done by specifying branches specifically. However, once we go to production with the feature, we likely want that enabled for all branches so that all of our non-production remote builds will have them enabled by default without needing their branches explicitly specified.This PR allows setting, for instance, a generic RX_ENABLED env var in Travis which can be applied to all branches as a fallback for branches not listed in the RX_ENABLED_BRANCHES variable.
If not set in Travis, the default value in our artifact.sh deployment script will be false, so it will not be accidentally deployed to production. When the time comes to deploy to production, we'll be able to simply set the
RX_ENABLEDvar in the Travis settings totruefor "All Branches" and we're good to go.I think this pattern will be flexible enough to suit our current needs and future feature flags as they come up.