Skip to content

feat!: use new eval/sync protos (requires flagd v0.7.3+) #762

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

Merged
merged 2 commits into from
Feb 13, 2024

Conversation

toddbaert
Copy link
Member

@toddbaert toddbaert commented Feb 13, 2024

  • use new evaluation.proto
  • use new sync.proto
  • requires usage of flagd v0.7.3+

Resolves: #743

Signed-off-by: Todd Baert <[email protected]>
@toddbaert toddbaert requested a review from a team as a code owner February 13, 2024 14:48
@github-actions github-actions bot requested a review from beeme1mr February 13, 2024 14:48
@beeme1mr
Copy link
Member

This is breaking only because it changes the minimum version of flagd, right?

@toddbaert toddbaert force-pushed the feat/new-protos-metadata branch from 1e4c97a to 16b17a8 Compare February 13, 2024 15:41
* use new evaluation.proto
* use new sync.proto
* requires usage of flagd v0.7.3+

Signed-off-by: Todd Baert <[email protected]>
@toddbaert
Copy link
Member Author

This is breaking only because it changes the minimum version of flagd, right?

Yes, it requires you to use a newer flagd; the break is in compatibility with external services, not anything in code.

@toddbaert toddbaert changed the title feat!: use new evaluation/sync protos feat!: use new eval/sync protos (requires flagd v0.7.3+) Feb 13, 2024
@toddbaert toddbaert merged commit 4da9deb into main Feb 13, 2024
@toddbaert toddbaert deleted the feat/new-protos-metadata branch February 13, 2024 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[flagd] use new protos
3 participants