Copying Feature Flags with Targeting User and/or rules #680
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 10 replies
-
|
Currently, we do not support copying targeting users and rules. For copying them, we need to consider
|
Beta Was this translation helpful? Give feedback.
-
|
If we are making complex targeting rules, what would you recommend be the
best way to eventually use the rule in production?
Thanh Nguyen
…On Mon, Nov 25, 2024 at 1:41 AM deleteLater ***@***.***> wrote:
Currently, we do not support copying targeting users and rules. For
copying them, we need to consider
- If the src flag's target users don’t exist in the target
environment, should we copy these users into the target environment?
- If the src flag contains a rule that using Segment, and this segment
doesn't exist in the target environment. Since the segment may also
reference environment users, making it hard/impossible to copy.
—
Reply to this email directly, view it on GitHub
<#680 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBIGWINVIJZISGXMYDPH5L2CLBA7AVCNFSM6AAAAABRSWGFI2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZWHA3TIOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello @deleteLater! I've recently started working with @thanh81 in featbit and am trying to migrate some very complex feature flags from Microsoft.FeatureManagement json files. Many of these were implemented from This is easily handled in featbit with the user attributes functionality.
This shouldn't be the default behavior, in most applications users don't span environments. It could be optional if other folks are interested in this behavior. It would make sense not to copy any rules which target users directly.
Like the above, segments could be copied only if they don't target specific users. Both of these scenarios could be handled by either altering the messaging about not copying targeting rules to say it will only not copy those with user targets or copying those rules with the user list empty and prompt the user to enter or delete the rule as necessary. In my experience, it's fairly rare to target segments of specific users when the system allows for access to the targeting criteria. It is also very time consuming and error prone to re-enter targeting rules across environments. It would be a huge boon to be able to copy these rules. If adding this to the featbit UI is undesirable, a workaround could also be achieved by exposing the APIs used to add targeting rules and user attributes so that we could script our own migration logic. This would also help us with copying targeting rules across separate featbit instances. |
Beta Was this translation helpful? Give feedback.


Related PR (#696) has been merged and this feature has been included in v4.2.1