-
Notifications
You must be signed in to change notification settings - Fork 41
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
fix: various clarifications #193
Conversation
* loosen shutdown requirements to support things like go ctx * clarify how to handle init/shutdown of providers bound to multiple names * clarify init function should terminate before provider used Signed-off-by: Todd Baert <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving - Open discussions can be finalized on agreements and personaly I don't see them to conflict a lot
Signed-off-by: Todd Baert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now and the changes are really good to me!
The spec shows that the initialization accepts a global context as a parameter. However the java sdk provider interface has the initialization API without any parameters. Is there any discussion regarding that? |
I think this is an oversight. I will open an issue in the Java SDK (we haven't released yet, so no issue). Great find. |
API.shutdown()
required in Go? #189clarify init function should terminate before provider used feat: add initialize and shutdown behavior java-sdk#456 (comment)cc @open-feature/technical-steering-committee @lopitz @lukas-reining @kinyoklion @Kavindu-Dodan
Definitely let me know anyone thinks something is missing or could be improved here.