-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Changing a feature flag defaultVariant
doesn't dynamically update services while demo is running
#1625
Comments
Hey @flands I've actually tested that on I know that for K8s, that may be different as we are not using the flagd operator, but for Docker it worked fine. |
@julianocosta89 Interesting! I'm on Darwin (ARM-based) running the latest Docker desktop. I tried the first two feature flags multiple times (for example |
Hey @flands, do you see an event in the flagd logs when you make a change in the config? Flagd uses fsnotify to detect changes. Perhaps your setup is triggering an event that we're currently not reacting to. |
We're considering more robust file watching approaches. |
It starts with the logs shown below and after changing the JSON file no new logs are recorded
|
I had the same experience (docker/macos/arm64/colima). To reliably switch the feature toggles both flagd and the service that uses the flag had to be restarted.
|
flagd |
Yes, version @Starefossen, thanks for bumping the version in the demo. |
* Upgrade flagd to v0.11.2 Close #1625 * Update opentelemetry-demo.yaml * Update docker-compose.yml
Bug Report
Which version of the demo you are using? 1.10.0
Symptom
Changing a feature flag
defaultVariant
while the demo application is running doesn't dynamically update servicesWhat is the expected behavior?
Changing a feature flag
defaultVariant
toon
while demo is running dynamically updates servicesWhat is the actual behavior?
Changing a feature flag
defaultVariant
toon
while demo is running is a noop.Reproduce
Per https://opentelemetry.io/docs/demo/feature-flags/, To enable a flag, change the defaultVariant value in the config file for a given flag to “on”, while the demo application is running edit
src/flagd/demo.flagd.json
and change adefaultVariant
toon
Additional Context
Perhaps this is expected behavior. If it is, then the documentation should be updated to state that if the demo application is running and a feature flag
defaultVariant
is changed then you need to restart the flagd service (make restart service=flagd
) or restart the demo application for it to take effect.I can make the documentation change if this is the recommended approach.
The text was updated successfully, but these errors were encountered: