-
Notifications
You must be signed in to change notification settings - Fork 51
[flagd] shutting down provider should reset the state. #410
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
Comments
@thiyagu06 I also see a potential improvement here. Though the spec 1 doesn't enforce a state change requirement after a shutdown, we can set the status to Feel free to open up a contribution PR on this. Footnotes |
Sure. I will work on this. |
Hey @thiyagu06 I'm going to unassign this from you for now, since we have an event coming up and KubeCon and it might be a good issue for people to take on. However, if you intend on completing it soon, let me know I will reassign to you. |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@toddbaert , I would like to contribute to this issue. Is it possible to assign it to me? |
@mehtasankets Assigned. |
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
…re#410) Signed-off-by: Sanket Mehta <[email protected]>
Signed-off-by: Sanket Mehta <[email protected]>
Fixed with #832 . Thank you @mehtasankets for the contribution 👍 |
https://github.com/open-feature/java-sdk-contrib/blob/main/providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/FlagdProvider.java#L56
It's not always guaranteed that
FeatureProvider.shutdown()
method is called at the end of application lifecycle. The user can call the shutdown method at any point in time of application lifetime. So it's better to reset the state. may be NOT_READY or new state and publish the event with the new state.The text was updated successfully, but these errors were encountered: