-
Notifications
You must be signed in to change notification settings - Fork 234
🚀 Announcing Flipt v2: Help Shape the Future of Flipt! #3828
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
Comments
For the following item:
CMIIW, this feature is already present in the cloud version right? |
Hey @agsha that is correct. We're bringing these capabilities into v2. |
Maybe Flipt can also support Remote Config stuff? |
@thepabloaguilar definitely! I think we just need more context on what specifically folks would want supported. Is it just storing a json blob as a first class thing (ie not having to nest it under a flag->metadata)? |
Feature Request: Hooks to plug in our own analytics systems in the client-sdk. So when using client side evaluation, during initialization of the engine, we can pass callbacks which will be invoked anytime there is a feature evaluation. We can implement the callback to write to our analytics backend (maybe BigQuery or kafka or some such) |
@agsha great shout! moving this to the client sdks repo to continue the discussion there |
This is a great time to drop |
Amazing! Will this remain an open-source? Feature request: streaming of config for GitOps client-side evaluation. |
@sw-tracker yes! It will remain open source and we will add support for streaming like we have in Flipt Cloud. We will add some enterprise features such as pull requests support and others that will require a license (paid) but the general functionality as it exists today will remain free and open source (including streaming) |
If you could include this one it would be amazing ! |
Yes we will! I just need to find some time to get it over the line |
Hi! As a feature request, it would be awesome for being able to combine individual user/entity configuration of a feature flag with the default flag resolution logic. That would allow us to provide a self-service for feature flags (mainly toggles) without needing a separate service to store this information. Even better if this works with the GitOps flow - developers keep using GitOps, while users can decide to opt-in on a feature behind a toggle. |
I'm not sure if anyone else has the same use case as us, but we are exclusively using read-only storage mode with declarative management ( Overall, we are thoroughly enjoying Flipt and looking forward to seeing v2! Especially the GitOps features. |
Hey @JanSvejda 👋🏻 Im not sure I fully understand what you're asking for, would you mind opening a new issue and tagging it as v2 with maybe a longer description or sketch of this feature? Thank you!! |
Hey @mitchs-dev ! Glad you are enjoying Flipt. I definitely think we can support webhook payloads for audit events for v2 (via writes to git from UI). The alpha version of v2 will likely not have audit event support because I'd like to rethink how it was implemented from teh ground up (not a huge fan of how it works today in v1). But it will come as a fast follow up. |
We’re excited to announce that we’ve started planning for Flipt v2, and we want your input to make it even better! 🎉
The high-level plan for Flipt v2 focuses on improving usability, flexibility, and compatibility while tackling key pain points from v1. Below is an overview of our current plan, including goals and non-goals.
This is a working document, and your feedback is crucial to ensure Flipt v2 meets the needs of the community. If you have ideas, concerns, or suggestions, please share them as comments on this issue. Let's make Flipt v2 a success together! 💬
📋 Development Plan
Goals
Non-Goals
🧠 We Need Your Input!
We’d love to hear your thoughts on:
To join the conversation, simply comment on this issue. You can also open a separate issue and tag it with
v2
if you want to dive deeper into a specific topic.Thank you for helping us make Flipt v2 the best it can be! 🚀
Feel free to suggest edits or raise any concerns below!
The text was updated successfully, but these errors were encountered: