Comments (5)
It strikes me that being able to override any feature as per @tmarkovski's approach should work.
Having looked through the source it looks like it comes down to this line where it requires the feature to be enabled otherwise it'll check for conditional features and find the settings loaded from appsettings.json
.
Here's a draft PR that enable supporting such an option.
from featuremanagement-dotnet.
We have similar requirements (sort of :) ) and we decided to use filter in a specific way and added IsEnabled field which controls a feature status.
{
"FeatureManagement": {
"FeatureA": {
"EnabledFor": [
{
"Name": "ProductPlan",
"Parameters": {
"IsEnabled": true,
"AllowedPlans": [
"Developer",
"Production",
"Enterprise"
]
}
}
]
}
}
}
from featuremanagement-dotnet.
Thanks @josephwoodward . I just assumed environment specific setting should work similarly as other settings. Your approach looks on point, thank you.
from featuremanagement-dotnet.
@tmarkovski I haven't seen this encountered yet but it is indeed an issue. A contributing factor to this issue is that when .NET Core composes the settings obtained from multiple json files it does not necessarily overwrite existing fields. This same behavior is going to cause a problem with the fix proposed by JosephWoodward. For example, if we start to short circuit evaluation because a feature is set to false how would we override it in a staging configuration? We would need to set the false to something else, maybe 'true'?
"FeatureManagement": {
"FeatureA": true,
"FeatureA": {
"EnabledFor": [
{
"Name": "ProductPlan",
"Parameters": {
"AllowedPlans": [
"Developer",
"Production",
"Enterprise"
]
}
}
]
}
}
But there are two problems with that.
- It looks odd to define FeatureA twice like that.
- 'true' would turn the feature on always, so really we would need to specify a value like "undefined" or really anything other than true or false.
This will need some thought to fix correctly and may require a change to the feature definition schema.
For now, the best way to address it without introducing another oddity is to do something like @leonids2005 is doing.
from featuremanagement-dotnet.
Sorry, my fault , I was not very attentive to change your definition
it should be
{
"FeatureManagement": {
"FeatureA": {
"EnabledFor": [
{
"Name": "ProductPlan",
"Parameters": {
"IsEnabled": true,
"AllowedPlans": [
"Developer",
"Production",
"Enterprise"
]
}
}
]
}
}
}
from featuremanagement-dotnet.
Related Issues (20)
- Suggest to have app.UseFeatureManagement HOT 8
- Silent failure in TargetingTelemetryInitializer HOT 10
- The TargetingId should be included in the FeatureEvaluation event even if it's null/empty. HOT 5
- Targeting evaluation is CPU dependent. HOT 4
- Remove the support for variants and telemetry from the .NET feature flag schema HOT 14
- Include Targeting Information on outgoing telemetry HOT 2
- Support .NET 8 Targeting framework in Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore
- Target netstandard2.* in Microsoft.FeatureManagement.Telemetry.ApplicationInsights
- The approach to telemetry (using custom `ITelemetryPublisher`) seems overengineered and counter to modern OpenTelemetry abstractions HOT 37
- Add Default Http Targeting Context Accessor
- Consider moving `TargetingHttpContextMiddleware` to the App Insights package HOT 2
- No instance of ITargetingContextAccessor is available for variant assignment. HOT 6
- FeatureManagerSnapshot should snapshot TargetingContext as well
- EvaluationDataToApplicationInsights example
- Can't Set FeatureFilters In FeatureManager In .NET Framework Application HOT 10
- Update Package metadata
- Add a link to preview on main readme HOT 1
- Cannot use the TargetingFilter in .NET class library project HOT 3
- Nuget "Microsoft.FeatureManagement.AspNetCore" Version 3.3.0 - Multiple feature filters match the configured filter named 'Microsoft.TimeWindow' HOT 8
- Consider using `TimeProvider` using Microsoft.Bcl.TimeProvider nuget package HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from featuremanagement-dotnet.