-
Notifications
You must be signed in to change notification settings - Fork 64
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: support new flagd.evaluation and flagd.sync schemas #1083
feat: support new flagd.evaluation and flagd.sync schemas #1083
Conversation
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
…hemas # Conflicts: # core/go.sum
Signed-off-by: Florian Bacher <[email protected]>
✅ Deploy Preview for polite-licorice-3db33c ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1083 +/- ##
==========================================
+ Coverage 72.93% 73.53% +0.59%
==========================================
Files 31 32 +1
Lines 2864 3113 +249
==========================================
+ Hits 2089 2289 +200
- Misses 670 717 +47
- Partials 105 107 +2 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
@bacherfl since you're going through this, would you mind sprinkling references to this new issue I created where relevant? That way it'll be super easy to make sure that we remove all the right stuff by just searching for |
I think the effort we should put into reducing duplication that we know will be deleted should be low, so unless the solutions are very easy, I'm fine with it as is. |
Can you update all e2e tests and documentation to use the new paths? I think a good approach might be to simply search for |
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.
thanks for the review, I will adapt the PR accordingly |
Signed-off-by: Florian Bacher <[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 great! Thanks a lot!
🤖 I have created a release *beep* *boop* --- <details><summary>flagd: 0.8.0</summary> ## [0.8.0](flagd/v0.7.2...flagd/v0.8.0) (2023-12-22) ### ⚠ BREAKING CHANGES * remove deprecated flags ([#1075](#1075)) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.2 ([#1056](#1056)) ([81e83ea](81e83ea)) * **deps:** update module github.com/spf13/viper to v1.18.0 ([#1060](#1060)) ([9dfa689](9dfa689)) ### 🧹 Chore * refactoring component structure ([#1044](#1044)) ([0c7f78a](0c7f78a)) * remove deprecated flags ([#1075](#1075)) ([49f6fe5](49f6fe5)) </details> <details><summary>flagd-proxy: 0.4.0</summary> ## [0.4.0](flagd-proxy/v0.3.2...flagd-proxy/v0.4.0) (2023-12-22) ### ⚠ BREAKING CHANGES * remove deprecated flags ([#1075](#1075)) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.2 ([#1056](#1056)) ([81e83ea](81e83ea)) * **deps:** update module github.com/spf13/viper to v1.18.0 ([#1060](#1060)) ([9dfa689](9dfa689)) ### 🧹 Chore * refactoring component structure ([#1044](#1044)) ([0c7f78a](0c7f78a)) * remove deprecated flags ([#1075](#1075)) ([49f6fe5](49f6fe5)) </details> <details><summary>core: 0.7.3</summary> ## [0.7.3](core/v0.7.2...core/v0.7.3) (2023-12-22) ### 🐛 Bug Fixes * **deps:** update golang.org/x/exp digest to 6522937 ([#1032](#1032)) ([78b23d2](78b23d2)) * **deps:** update module connectrpc.com/connect to v1.13.0 ([#1070](#1070)) ([63f86ea](63f86ea)) * **deps:** update module github.com/diegoholiveira/jsonlogic/v3 to v3.4.0 ([#1068](#1068)) ([5c5d5ab](5c5d5ab)) * **deps:** update module github.com/open-feature/open-feature-operator to v0.5.2 ([#1059](#1059)) ([cefea3e](cefea3e)) * **deps:** update module google.golang.org/grpc to v1.60.0 ([#1074](#1074)) ([bf3e9d8](bf3e9d8)) * **deps:** update module google.golang.org/grpc to v1.60.1 ([#1092](#1092)) ([5bf1368](5bf1368)) * make sure sync builder is initialized to avoid nil pointer access ([#1076](#1076)) ([ebcd616](ebcd616)) ### ✨ New Features * support new flagd.evaluation and flagd.sync schemas ([#1083](#1083)) ([e9728aa](e9728aa)) ### 🧹 Chore * refactoring component structure ([#1044](#1044)) ([0c7f78a](0c7f78a)) * renaming of evaluation components ([#1064](#1064)) ([d39f31d](d39f31d)) * use client-go library for retrieving FeatureFlag CRs ([#1077](#1077)) ([c86dff0](c86dff0)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Closes #1029
This PR introduces support for the newly introduced evaluation and sync schemas.
Supporting both the old and new schemas involves some duplication, but I tried to keep it as minimal as possible. I'm of course open for suggestions for any ideas on how to make this simpler :)
See reasoning for new naming here.