-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “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? Sign in to your account
Update dependency Microsoft.FeatureManagement to v4 - autoclosed #1172
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Terraform environment AT21Format and Style 🖌
|
Context | Values |
---|---|
Pusher | @renovate[bot] |
Action | push |
Working Directory | ./infrastructure/shared |
State File | github.com/altinn/altinn-authorization/environments/at21/infrastructure.tfstate |
Plan File | github.com_altinn_altinn-authorization_environments_at21_infrastructure.tfstate.tfplan |
Terraform environment AT22Format and Style 🖌
|
Context | Values |
---|---|
Pusher | @renovate[bot] |
Action | push |
Working Directory | ./infrastructure/shared |
State File | github.com/altinn/altinn-authorization/environments/at22/infrastructure.tfstate |
Plan File | github.com_altinn_altinn-authorization_environments_at22_infrastructure.tfstate.tfplan |
Terraform environment AT24Format and Style 🖌
|
Context | Values |
---|---|
Pusher | @renovate[bot] |
Action | push |
Working Directory | ./infrastructure/shared |
State File | github.com/altinn/altinn-authorization/environments/at24/infrastructure.tfstate |
Plan File | github.com_altinn_altinn-authorization_environments_at24_infrastructure.tfstate.tfplan |
Terraform environment AT23Format and Style 🖌
|
Context | Values |
---|---|
Pusher | @renovate[bot] |
Action | push |
Working Directory | ./infrastructure/shared |
State File | github.com/altinn/altinn-authorization/environments/at23/infrastructure.tfstate |
Plan File | github.com_altinn_altinn-authorization_environments_at23_infrastructure.tfstate.tfplan |
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
from
November 7, 2024 10:02
263fbe2
to
52f40bf
Compare
Quality Gate passedIssues Measures |
lovoll
approved these changes
Nov 7, 2024
renovate
bot
changed the title
Update dependency Microsoft.FeatureManagement to v4
Update dependency Microsoft.FeatureManagement to v4 - autoclosed
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.5.0
->4.0.0
Release Notes
microsoft/FeatureManagement-Dotnet (Microsoft.FeatureManagement)
v4.0.0
Compare Source
4.0.0 - November 1, 2024
Microsoft.FeatureManagement Updates
The packages associated with this release are
Microsoft.FeatureManagement
Enhancements
Variant Feature Flags
A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
The new
IVariantFeatureManager
has been introduced as the successor to the existingIFeatureManager
. It retains all the functionalities ofIFeatureManager
while adding newGetVariantAsync
methods and supportingCancellationToken
for all methods.Note: If reading variant flags from App Configuration, version
8.0.0
or above for theMicrosoft.Extensions.Configuration.AzureAppConfiguration
orMicrosoft.Azure.AppConfiguration.AspNetCore
package is required.For more details on Variants, see here.
Variant Service Provider
Variant feature flags can be used in conjunction with dependency injection to surface different implementations of a service for different users. This is accomplished by using the Variant Service Provider.
For more details on Variant Service Provider, see here
Telemetry
Telemetry provides observability into flag evaluations, offering insights into which users received specific flag results. This enables more powerful metric analysis, such as experimentation.
For more details on Telemetry, see here.
Microsoft Feature Management Schema
Added support for variant feature flags defined using Microsoft Feature Management schema. Variants and telemetry can be declared using Microsoft Feature Flag schema v2. Here is a Sample.
Performance Optimizations
The performance of the feature flag state evaluation has been improved by up to 20%, with a memory reduction of up to 30% for .NET 8 applications compared to the version 3.5.0 release.
Microsoft.FeatureManagement.AspNetCore
Enhancements
Adjusted the
.WithTargeting()
builder method to automatically addHttpContextAccessor
if it's not already added.Added
TargetingHttpContextMiddleware
which persists targeting context in the current activity. This is used when setting up Telemetry.Added support for variants in
FeatureTagHelper
. This allows MVC views to use the<feature>
tag to conditionally render content based on whether a specific variant of a feature is assigned.For more details on ASP.NET views and variants, see here.
Updated
Microsoft.FeatureManagement
reference to4.0.0
. See the release notes for more information on the changes.Added support for .NET 9 as a target framework.
Breaking Change
FeatureTagHelper
constructor now requires anIVariantFeatureManager
to support new variant functionality. While this class is typically not instantiated directly, any direct instantiation will need to be updated.Microsoft.FeatureManagement.Telemetry.ApplicationInsights
Enhancements
Added support for Application Insights telemetry. To publish feature flag evaluation data and tag outgoing events with targeting information, register the Application Insights telemetry publisher as shown below.
For more details on Application Insights Publishing, see here
Configuration
📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.