You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openfeature-provider/go/README.md
+113Lines changed: 113 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,7 @@ The `ProviderConfig` struct contains all configuration options for the provider:
86
86
#### Optional Fields
87
87
88
88
-`Logger` (*slog.Logger): Custom logger for provider operations. If not provided, a default text logger is created. See [Logging](#logging) for details.
89
+
-`StickyResolveStrategy` (StickyResolveStrategy): Strategy for handling sticky resolve scenarios. Defaults to `RemoteResolverFallback`. See [Sticky Resolve](#sticky-resolve) for details.
89
90
-`ResolverStateServiceAddr` (string): Custom address for the resolver state service. Defaults to `edge-grpc.spotify.com`
90
91
-`FlagLoggerServiceAddr` (string): Custom address for the flag logger service. Defaults to `edge-grpc.spotify.com`
91
92
-`AuthServiceAddr` (string): Custom address for the auth service. Defaults to `edge-grpc.spotify.com`
**Important**: This configuration disables automatic state fetching and exposure logging. For production deployments, always use `NewProvider()` with `ProviderConfig`.
112
113
114
+
## Sticky Resolve
115
+
116
+
Sticky Resolve ensures users receive the same variant throughout an experiment, even if their targeting attributes change or you pause new assignments.
117
+
118
+
**Two main use cases:**
119
+
1.**Consistent experience** - User moves countries but keeps the same variant
120
+
2.**Pause intake** - Stop new assignments while maintaining existing ones
0 commit comments