🙏 If you are using GO Feature Flag please consider to add yourself in the adopters list.
This simple act significantly boosts the project's visibility and credibility, making a substantial contribution to its advancement.
- 🎛️ GO Feature Flag
- How can I contribute?
GO Feature Flag is a lightweight and open-source solution that provides a simple and complete feature flag implementation.
The solution has been built to facilitate the usage of feature flags in your code without having to contact any vendor.
Originally, GO Feature Flag was designed as a solution exclusively for the GO language. With the new standardization of feature flags by the Openfeature project, the solution is now available for multiple languages (list of supported languages) through a simple API server called the relay proxy, which can be hosted.
ℹ️ Info
If you are not familiar with feature flags, I've written an article which explains why feature flags can fasten your iteration cycle.
- Storing your configuration flags file on various locations (
HTTP,S3,Kubernetes, see full list). - Configuring your flags in various format (
JSON,TOMLandYAML). - Adding complex rules to target your users.
- Use a complex rollout strategy for your flags :
- Exporting your flags usage data to various destinations such as (
S3,Google cloud storage,file, see the full list). - Getting notified when a flag has been changed (
webhookandslack). - Use GO Feature Flag in several languages with Open Feature SDKs.
go-feature-flag-demo.mp4
The code of this demo is available in examples/demo repository.
Before starting to use GO Feature Flag you should decide if you want to use the GO Module directly or if you want to install the relay proxy.
The GO module is ideal for using GO Feature Flag exclusively in GO projects. If your project involves multiple languages, we recommend using the Open Feature SDKs.
Using the GO Module
go get github.com/thomaspoignant/go-feature-flagCreate a new YAML file containing your first flag configuration.
# 20% of the users will use the variation "my-new-feature"
test-flag:
variations:
my-new-feature: true
my-old-feature: false
defaultRule:
percentage:
my-new-feature: 20
my-old-feature: 80This flag split the usage of this flag, 20% will use the variation my-new-feature and 80% the variation my-old-feature.
First, you need to initialize the ffclient with the location of your backend file.
err := ffclient.Init(ffclient.Config{
PollingInterval: 3 * time.Second,
Retriever: &fileretriever.Retriever{
Path: "flag-config.goff.yaml",
},
})
defer ffclient.Close()This example will load a file from your local computer and will refresh the flags every 3 seconds (if you omit the PollingInterval, the default value is 60 seconds).
ℹ info
This is a basic configuration to test locally, in production it is better to use a remote place to store your feature flag configuration file.
Look at the list of available options in the Store your feature flag file page.
Now you can evaluate your flags anywhere in your code.
user := ffcontext.NewEvaluationContext("user-unique-key")
hasFlag, _ := ffclient.BoolVariation("test-flag", user, false)
if hasFlag {
// flag "test-flag" is true for the user
} else {
// flag "test-flag" is false for the user
}The full documentation is available on https://docs.gofeatureflag.org
You can find more examples in the examples/ directory.
Using Open Feature SDKs
Create a new YAML file containing your first flag configuration.
# 20% of the users will use the variation "my-new-feature"
test-flag:
variations:
my-new-feature: true
my-old-feature: false
defaultRule:
percentage:
my-new-feature: 20
my-old-feature: 80This flag split the usage of this flag, 20% will use the variation my-new-feature and 80% the variation my-old-feature.
Create a new YAML file containing the configuration of your relay proxy.
listen: 1031
pollingInterval: 1000
startWithRetrieverError: false
retriever:
kind: file
path: /goff/flag-config.yaml
exporter:
kind: logAnd we will run the relay proxy locally to make the API available.
The default port will be 1031.
# Launch the container
docker run \
-p 1031:1031 \
-v $(pwd)/flag-config.yaml:/goff/flag-config.yaml \
-v $(pwd)/goff-proxy.yaml:/goff/goff-proxy.yaml \
gofeatureflag/go-feature-flag:latest
If you don't want to use docker to install the relay proxy you can go to docker hub.
In this example, we are using the javascript SDK, but it is still relevant for all the languages.
npm i @openfeature/server-sdk @openfeature/go-feature-flag-providerIn your app initialization you have to create a client using the Open Feature SDK and initialize it.
const {OpenFeature} = require("@openfeature/server-sdk");
const {GoFeatureFlagProvider} = require("@openfeature/go-feature-flag-provider");
// init Open Feature SDK with GO Feature Flag provider
const goFeatureFlagProvider = new GoFeatureFlagProvider({
endpoint: 'http://localhost:1031/' // DNS of your instance of relay proxy
});
OpenFeature.setProvider(goFeatureFlagProvider);
const featureFlagClient = OpenFeature.getClient('my-app')Now you can evaluate your flags anywhere in your code using this client.
// Context of your flag evaluation.
// With GO Feature Flag you MUST have a targetingKey that is a unique identifier of the user.
const userContext = {
targetingKey: '1d1b9238-2591-4a47-94cf-d2bc080892f1', // user unique identifier (mandatory)
firstname: 'john',
lastname: 'doe',
email: '[email protected]',
admin: true, // this field is used in the targeting rule of the flag "flag-only-for-admin"
// ...
};
const adminFlag = await featureFlagClient.getBooleanValue('flag-only-for-admin', false, userContext);
if (adminFlag) {
// flag "flag-only-for-admin" is true for the user
console.log("new feature");
} else {
// flag "flag-only-for-admin" is false for the user
}Originally GO Feature Flag was built to be a GOlang only library, but it limits the ecosystem too much.
To be compatible with more languages we have implemented the GO Feature Flag Relay Proxy.
It is a service you can host that provides an API to evaluate your flags, you can call it using HTTP to get your variation.
Since we believe in standardization we are also implementing OpenFeature providers to interact with this API in the language of your choice.
(OpenFeature is still at an early stage, so not all languages are supported and expect some changes in the future)
For now, we have providers for:
| Language | Provider |
|---|---|
| Go | Go Provider |
| Java | Java Provider |
| Kotlin / Android | Kotlin Provider  |
| Javascript/Typescript | Server provider / Client provider |
| PHP | Not currently available help by contributing here |
| Python | Python provider |
| .Net | .Net Provider |
| Ruby | Not currently available help by contributing here |
The module supports different ways of retrieving the flag file.
The available retrievers are:
- GitHub
- GitLab
- HTTP endpoint
- AWS S3
- Local file
- Google Cloud Storage
- Kubernetes ConfigMaps
- MongoDB
- Redis
See the full list and more information.
GO Feature Flag core feature is to centralize all your feature flags in a single file and to avoid hosting and maintaining a backend server to manage them.
Your file should be a YAML, JSON or TOML file with a list of flags (examples: YAML, JSON, TOML).
The easiest way to create your configuration file is to use GO Feature Flag Editor available at https://editor.gofeatureflag.org.
If you prefer to do it manually please follow the instruction below.
A flag configuration looks like this:
YAML
# This is your configuration for your first flag
first-flag:
variations: # All possible return value for your feature flag
A: false
B: true
targeting: # If you want to target a subset of your users in particular
- query: key eq "random-key"
percentage:
A: 0
B: 100
defaultRule: # When no targeting match we use the defaultRule
variation: A
# A second example of a flag configuration
second-flag:
variations:
A: "valueA"
B: "valueB"
defaultValue: "a default value"
targeting:
- name: notkey_rule
query: key eq "not-a-key"
percentage:
A: 10
B: 90
defaultRule:
variation: defaultValue
version: "12"
experimentation:
start: 2021-03-20T00:00:00.1-05:00
end: 2021-03-21T00:00:00.1-05:00JSON
{
"first-flag": {
"variations": {
"A": false,
"B": true
},
"targeting": [
{
"query": "key eq \"random-key\"",
"percentage": {
"A": 0,
"B": 100
}
}
],
"defaultRule": {
"variation": "A"
}
},
"second-flag": {
"variations": {
"A": "valueA",
"B": "valueB",
"defaultValue": "a default value"
},
"targeting": [
{
"name": "notkey_rule",
"query": "key eq \"not-a-key\"",
"percentage": {
"A": 10,
"B": 90
}
}
],
"defaultRule": {
"variation": "defaultValue"
},
"version": "12",
"experimentation": {
"start": "2021-03-20T05:00:00.100Z",
"end": "2021-03-21T05:00:00.100Z"
}
}
}TOML
[first-flag.variations]
A = false
B = true
[[first-flag.targeting]]
query = 'key eq "random-key"'
[first-flag.targeting.percentage]
A = 0
B = 100
[first-flag.defaultRule]
variation = "A"
[second-flag]
version = "12"
[second-flag.variations]
A = "valueA"
B = "valueB"
defaultValue = "a default value"
[[second-flag.targeting]]
name = "notkey_rule"
query = 'key eq "not-a-key"'
[second-flag.targeting.percentage]
A = 10
B = 90
[second-flag.defaultRule]
variation = "defaultValue"
[second-flag.experimentation]
start = 2021-03-20T05:00:00.100Z
end = 2021-03-21T05:00:00.100ZFor detailed information on the fields required to create a flag, please refer to the documentation.
The query format is based on the nikunjy/rules library.
All the operations can be written in capitalized or lowercase (ex: eq or EQ can be used).
Logical Operations supported are AND OR.
Compare Expression and their definitions (a|b means you can use either one of the two a or b):
eq|==: equals to
ne|!=: not equals to
lt|<: less than
gt|>: greater than
le|<=: less than equal to
ge|>=: greater than equal to
co: contains
sw: starts with
ew: ends with
in: in a list
pr: present
not: not of a logical expression
- Select a specific user:
key eq "[email protected]" - Select all identified users:
anonymous ne true - Select a user with a custom property:
userId eq "12345"
Feature flag targeting and rollouts are all determined by the user you pass to your evaluation calls.
The only required field for a user is his unique key, it is used by the internals of GO Feature Flag to do a hash to define
if the flag can apply to this user or not.
You can use a primary key, an e-mail address, or a hash, as long as the same user always has the same key.
We recommend using a hash if possible.
All the other attributes are optional.
Since it is useful to make complex queries on your flag, you can add as many information fields you want to your user. It will be used when testing the targeting rules.
You can also distinguish logged-in users from anonymous users in the SDK (check documentation about anonymous users).
The Variation methods determine whether a flag is enabled or not for a specific user.
GO Feature Flag can manage more than just boolean values; the value of your flag can be any of the following types:
boolintfloatstringjson arrayjson object
result, _ := ffclient.BoolVariation("your.feature.key", user, false)
// result is now true or false depending on the setting of
// this boolean feature flagVariation methods take the feature flag key, a user, and a default value.
The default value is returned when an error is encountered (ffclient not initialized, variation with wrong type, flag does not exist ...).
In the example, if the flag your.feature.key does not exist, the result will be false.
Note that the result will always provide a usable value.
If you want to send the information about a specific user to a front-end, you will want a snapshot of all the flags for this user at a specific time.
The method ffclient.AllFlagsState returns a snapshot of flag values and metadata.
The function is evaluating all available flags for the user and returns a flagstate.AllFlagsState object containing the
information you need.
The MarshalJSON() function will return a JSON Object, that can be directly used by your front-end application.
More details in the documentation.
A critical part of every new feature release is orchestrating the actual launch schedule between the Product, Engineering, and Marketing teams.
Delivering powerful user experiences typically requires software teams to manage complex releases and make manual updates at inconvenient times.
But it does not have to, having a complex rollout strategy allows you to have a lifecycle for your flags.
- Canary releases - impact randomly a subset of your users.
- Progressive rollout - increase the percentage of your flag over time.
- Scheduled rollout - update your flag over time.
- Experimentation rollout - serve your feature only for a determined time (perfect for A/B testing).
If you want to be informed when a flag has changed, you can configure a notifier.
A notifier will send one notification to the targeted system to inform them that a new flag configuration has been loaded.
ℹ️ GO Feature Flag can handle more than one notifier at a time.
Available notifiers are:
- Slack
- Webhook
GO Feature Flag allows you to export data about the usage of your flags.
It collects all variation events and can save these events in several locations:
- Local file - create local files with the variation usages.
- Log - use your logger to write the variation usages.
- AWS S3 - export your variation usages to S3.
- Google Cloud Storage - export your variation usages to Google Cloud Storage.
- Webhook - export your variation usages by calling a webhook.
- AWS SQS - export your variation usages by sending events to SQS.
- Google PubSub - export your variation usages by publishing events to PubSub topic.
Currently, we are supporting only feature events.
It represents individual flag evaluations and is considered "full fidelity" events.
An example feature event below:
{
"kind": "feature",
"contextKind": "anonymousUser",
"userKey": "ABCD",
"creationDate": 1618228297,
"key": "test-flag",
"variation": "Default",
"value": false,
"default": false,
"source": "SERVER"
}The format of the data is described in the documentation. Events are collected and sent in bulk to avoid spamming your exporter.
A command line tool is available to help you lint your configuration file: go-feature-flag-lint.
This project welcomes contributions from the community. If you're interested in contributing, see the contributors' guide for some helpful tips.
Thanks so much to our contributors.
If you are using go-feature-flag, we encourage you to include your company's name in this list. This simple act significantly boosts the project's visibility and credibility, making a substantial contribution to its advancement. To do so, kindly add yourself to adopters.
Here is the list of adopters.
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent