-
Notifications
You must be signed in to change notification settings - Fork 45
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
feat: [flagd] Default port to 8015 if in-process resolver is used. #810
feat: [flagd] Default port to 8015 if in-process resolver is used. #810
Conversation
5f2a504
to
4f693de
Compare
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.
Overall, LGTM
Thanks @zedadyna for your contribution. Before merging, I think we should address the discussion on how to test env var and if we should move this to a dedicated ticket 🤔
providers/flagd/src/test/java/dev/openfeature/contrib/providers/flagd/FlagdOptionsTest.java
Show resolved
Hide resolved
providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/Config.java
Outdated
Show resolved
Hide resolved
providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/FlagdOptions.java
Outdated
Show resolved
Hide resolved
providers/flagd/src/test/java/dev/openfeature/contrib/providers/flagd/FlagdOptionsTest.java
Show resolved
Hide resolved
providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/FlagdOptions.java
Show resolved
Hide resolved
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.
Thank you @zedadyna for working on this. I left few nits, othwerwise this is a good improvement :)
Ohh and the build fails because of checkstyle [1]. You can run and validate this locallly with mvn org.apache.maven.plugins:maven-checkstyle-plugin:3.4.0:check
Yes @zedadyna the build is failing because you're missing some javadoc:
|
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.
Agree with some of the minor feedback in here. If we want to discuss env testing a bit more, that can be in a new issue.
Approving, but you'll have to fix the CI issue first.
b47731d
to
6eaa321
Compare
6eaa321
to
1125869
Compare
closes: open-feature#809 Signed-off-by: Daniel Zehetner <daniel.zehetner@dynatrace.com> Co-authored-by: Alexandra Oberaigner <alexandra.oberaigner@dynatrace.com> Signed-off-by: Daniel Zehetner <daniel.zehetner@dynatrace.com>
…ments Signed-off-by: Daniel Zehetner <daniel.zehetner@dynatrace.com>
1125869
to
72e9bf6
Compare
created #818 to discuss the env testing topic |
closes: #809
This PR
The flagd provider defaults to RPC mode and the corresponding port (8013) using the evaluation proto. If the in-process resolver is selected, it operates in in-process mode using the sync proto, but still uses port 8013, instead of defaulting to the correct port (8015, for the sync proto).
We improve the configuration by defaulting to port 8015 if the in-process resolver is selected.
Related Issues
Fixes #809