Skip to content

Hook for Changed Features #27

Description

@MarwinMoellers

Is your feature request related to a problem? Please describe.

When Programming reactively or asyncronusly it is only interesting to know when a Feature has changed.
I don't believe the (...)Async Endpoints are helpful here.

Describe the solution you'd like

I would like to be notified when the value of a Feature Toggle/Config is Changed.
Optimally I would like to listen to Spring Application Events.

Describe alternatives you've considered

Alternatively a simple Oberserver-Pattern would be fine.
Or any other Pub-Sub Pattern.

Additional context

We are using it with Spring Gateway, and want to change the Routing during Runtime based on the Toggles State.

Activity

  1. z4kn4fein commented on Mar 7, 2023

    @z4kn4fein
    Member

    Hi @MarwinMoellers, thank you for the suggestion!
    Currently, the SDK doesn't track changes for individual feature flags, only for the whole config. I assume you already know this, but it can only send the modified Map<string, Setting> map to the user via the onConfigChanged hook.

    I'll put this topic on our next dev meeting's agenda to discuss it with the team. I'll let you know about the results.

  2. MarwinMoellers commented on Mar 7, 2023

    @MarwinMoellers
    Author

    Hey @z4kn4fein, thanks for the quick response.
    We'll construct it for ourself then. Once the hooks work 👍
    But I think there might be more widespread use for this feature.

  3. z4kn4fein commented on Mar 21, 2023

    @z4kn4fein
    Member

    Hey @MarwinMoellers , we discussed your suggestion and agreed that it would be a valuable feature to notify clients about which feature flags have been changed. We put a ticket about that on our SDK development board and will implement it soon in each SDK.

  4. github-actions commented on Apr 12, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

  5. github-actions commented on May 4, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

  6. github-actions commented on May 26, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

  7. adams85 commented on May 31, 2023

    @adams85
    Contributor

    Hi @MarwinMoellers,

    FYI, we added this feature request to our public roadmap, however we don't expect it earlier than Q4.

  8. 3 remaining items

  9. github-actions commented on Aug 14, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

  10. github-actions commented on Sep 5, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

  11. github-actions commented on Sep 27, 2023

    @github-actions

    This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    do-not-staleStale workflow skips issues with this label.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions