🚀 Announcing Flipt v2: Help Shape the Future of Flipt!

[markphelps]

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

• Declarative storage backend: Remove database dependencies for flag state.
• GitOps workflows: Full support, including write operations.
• API compatibility: Maintain compatibility with current Flipt Evaluation APIs.
• Simplified configuration: Consolidate/remove unnecessary options.
• Authentication improvements: Support for Redis and in-memory backends.
• Declarative API: New API for managing flag configuration.
• Legacy cleanup: Remove legacy evaluation APIs and address v1 issues.
• UI enhancements: Improve where necessary.
• Optional features:
  • Support write operations to object storage backends.
  • Enable approval workflows for Git-based setups.

Non-Goals

• Compatibility with current Flipt Management APIs.
• Backward compatibility with v1 configuration files.
• Changes to v1 base types (flags, segments, etc.).

🧠 We Need Your Input!

We’d love to hear your thoughts on:

1. What features or improvements would you like to see in Flipt v2?
2. Do the goals align with your needs as a user or contributor?
3. Are there areas you think should be prioritized during development?
4. Is there anything else you'd like to share?

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!

[agsha]

For the following item:

GitOps workflows: Full support, including write operations

CMIIW, this feature is already present in the cloud version right?

[GeorgeMac]

Hey @agsha that is correct. We're bringing these capabilities into v2.

[thepabloaguilar]

Maybe Flipt can also support Remote Config stuff?

[markphelps]

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)?

[agsha]

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)

[markphelps]

@agsha great shout! moving this to the client sdks repo to continue the discussion there

[erka]

This is a great time to drop /meta/config endpoint.

[sw-tracker]

GitOps workflows: Full support, including write operations.

Amazing! Will this remain an open-source?

Feature request: streaming of config for GitOps client-side evaluation.

[markphelps]

GitOps workflows: Full support, including write operations.

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)