You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
There are currently one flag and one switch being used in production, but they are not present in local db.
those flags/switches should be part of the project setup, to avoid production/development disparity.
The text was updated successfully, but these errors were encountered:
@yotammanor I'm not sure about that.. we certainly don't want them in "initial_data.json" automatically loaded on migration, thus production would be rolled to hard coded state every deploy+migration. So maybe dump a JSON fixture, to be used only in local dev and add it to the setup instructions?
And of course, this would never be updated when actual flag changes, and would cause dispartiy all over the place.. :(
The correct way to solve this is probably using some kind of configuration service, with different production, staging, dev environment, that should handle this kind of feature flags. But we are certainly not there..
I think the current setup is the best of bad options, until we move to a configuration service.
There are currently one flag and one switch being used in production, but they are not present in local db.
those flags/switches should be part of the project setup, to avoid production/development disparity.
The text was updated successfully, but these errors were encountered: