OpenFeature Go SDK
👋 Hey there! Thanks for checking out the OpenFeature Go SDK
What is OpenFeature?
OpenFeature is an open standard that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool.
Why standardize feature flags?
Standardizing feature flags unifies tools and vendors behind a common interface which avoids vendor lock-in at the code level. Additionally, it offers a framework for building extensions and integrations and allows providers to focus on their unique value proposition.
🔍 Requirements:
- Go 1.18+
📦 Installation:
go get github.com/open-feature/go-sdkSoftware Bill of Materials (SBOM)
The release workflow generates an SBOM (using cyclonedx) and pushes it to the release. It can be found as an asset named bom.json within a release.
🌟 Features:
- support for various backend providers
- easy integration and extension via hooks
- bool, string, numeric, and object flag types
- context-aware evaluation
🚀 Usage:
Basics:
To configure the SDK you'll need to add a provider to the openfeature global singleton. From there, you can generate a Client which is usable by your code.
While you'll likely want a provider for your specific backend, we've provided a NoopProvider, which simply returns the default passed in.
package main
import (
"context"
"github.com/open-feature/go-sdk/pkg/openfeature"
)
func main() {
openfeature.SetProvider(openfeature.NoopProvider{})
client := openfeature.NewClient("app")
value, err := client.BooleanValue(
context.Background(), "v2_enabled", false, openfeature.EvaluationContext{},
)
}A list of available providers can be found here.
For complete documentation, visit: https://openfeature.dev/docs/category/concepts
Context-aware evaluation:
Sometimes the value of a flag must take into account some dynamic criteria about the application or user, such as the user location, IP, email address, or the location of the server.
In OpenFeature, we refer to this as targeting.
If the flag system you're using supports targeting, you can provide the input data using the EvaluationContext.
// add a value to the global context
openfeature.SetEvaluationContext(openfeature.NewEvaluationContext(
"foo",
map[string]interface{}{
"myGlobalKey": "myGlobalValue",
},
))
// add a value to the client context
client := openfeature.NewClient("my-app")
client.SetEvaluationContext(openfeature.NewEvaluationContext(
"",
map[string]interface{}{
"myGlobalKey": "myGlobalValue",
},
))
// add a value to the invocation context
evalCtx := openfeature.NewEvaluationContext(
"",
map[string]interface{}{
"myInvocationKey": "myInvocationValue",
},
)
boolValue, err := client.BooleanValue("boolFlag", false, evalCtx)Providers:
To develop a provider, you need to create a new project and include the OpenFeature SDK as a dependency. This can be a new repository or included in the existing contrib repository available under the OpenFeature organization. Finally, you’ll then need to write the provider itself. This can be accomplished by implementing the FeatureProvider interface exported by the OpenFeature SDK.
package provider
// MyFeatureProvider implements the FeatureProvider interface and provides functions for evaluating flags
type MyFeatureProvider struct{}
// Metadata returns the metadata of the provider
func (e MyFeatureProvider) Metadata() Metadata {
return Metadata{Name: "MyFeatureProvider"}
}
// BooleanEvaluation returns a boolean flag
func (e MyFeatureProvider) BooleanEvaluation(flag string, defaultValue bool, evalCtx EvaluationContext) BoolResolutionDetail {
// code to evaluate boolean
}
// StringEvaluation returns a string flag
func (e MyFeatureProvider) StringEvaluation(flag string, defaultValue string, evalCtx EvaluationContext) StringResolutionDetail {
// code to evaluate string
}
// FloatEvaluation returns a float flag
func (e MyFeatureProvider) FloatEvaluation(flag string, defaultValue float64, evalCtx EvaluationContext) FloatResolutionDetail {
// code to evaluate float
}
// IntEvaluation returns an int flag
func (e MyFeatureProvider) IntEvaluation(flag string, defaultValue int64, evalCtx EvaluationContext) IntResolutionDetail {
// code to evaluate int
}
// ObjectEvaluation returns an object flag
func (e MyFeatureProvider) ObjectEvaluation(flag string, defaultValue interface{}, evalCtx EvaluationContext) ResolutionDetail {
// code to evaluate object
}
// Hooks returns hooks
func (e MyFeatureProvider) Hooks() []Hook {
// code to retrieve hooks
}See here for a catalog of available providers.
Hooks:
Implement your own hook by conforming to the Hook interface.
To satisfy the interface, all methods (Before/After/Finally/Error) need to be defined. To avoid defining empty functions
make use of the UnimplementedHook struct (which already implements all the empty functions).
type MyHook struct {
openfeature.UnimplementedHook
}
// overrides UnimplementedHook's Error function
func (h MyHook) Error(hookContext openfeature.HookContext, err error, hookHints openfeature.HookHints) {
log.Println(err)
}Register the hook at the global, client, or invocation level.
A list of available hooks can be found here.
Logging:
If not configured, the logger falls back to the standard Go log package at error level only.
In order to avoid coupling to any particular logging implementation the SDK uses the structured logging logr API. This allows integration to any package that implements the layer between their logger and this API. Thankfully there are already integration implementations for many of the popular logger packages.
var l logr.Logger
l = integratedlogr.New() // replace with your chosen integrator
openfeature.SetLogger(l) // set the logger at global level
c := openfeature.NewClient("log").WithLogger(l) // set the logger at client levellogr uses incremental verbosity levels (akin to named levels but in integer form).
The SDK logs info at level 0 and debug at level 1. Errors are always logged.
⭐️ Support the project
- Give this repo a
⭐️ ! - Follow us on social media:
- Twitter: @openfeature
- LinkedIn: OpenFeature
- Join us on Slack
- For more, check out our community page
🤝 Contributing
Interested in contributing? Great, we'd love your help! To get started, take a look at the CONTRIBUTING guide.
Thanks to everyone that has already contributed
Made with contrib.rocks.