GO Feature Flag is a simple, complete and lightweight self-hosted feature flag solution 100% Open Source. 🎛️
MIT License
Bot releases are visible (Hide)
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
version
field for the flagsPublished by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
AllFlagsState
to get all flag value for a specific user.golint
by revive
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
experimentation
property under the rollout
key.Published by thomaspoignant over 3 years ago
⚠️ feature #105 is a breaking change, the repartition will work as expected BUT you may have some changes for specific users. A user who was affected by a flag is not guaranteed to still be affected.
This breaking change is needed to unblock future features like #101.
We accept this breaking change only because we are still in version v0.X
, as soon as we hit the v1.X
this kind of change will not be possible.
startDate
and an endDate
for the flag.PayloadURL
is deprecated and you should use EndpointURL
instead.Published by thomaspoignant over 3 years ago
fflog
to always add the datePublished by thomaspoignant over 3 years ago
err := Init(Config{
// ...
DataExporter: DataExporter{
Exporter: &ffexporter.Log{},
},
})
Published by thomaspoignant over 3 years ago
This new version includes a way to export your data to a file 💥 📈 📊 💹
Ok maybe you don't care to collect data on the fly and to put them locally, but this version includes a simple way to add more exporters in the future.
This version will allow developing #89 #88 #87 ...
Published by thomaspoignant over 3 years ago
Published by thomaspoignant over 3 years ago
Webhooks
field in the configuration to have the field Notifiers
insteadIf you were using Webhooks
before, you should have a configuration like this:
ffclient.Init(ffclient.Config{
Retriever: &ffclient.FileRetriever{Path: "testdata/flag-config.yaml"},
FileFormat: "yaml",
Webhooks: []ffclient.WebhookConfig{
{
PayloadURL: " https://example.com/hook",
Secret: "Secret",
Meta: map[string]string{
"app.name": "my app",
},
},
},
}
With Notifiers
, your configuration should looks like this now:
ffclient.Init(ffclient.Config{
Retriever: &ffclient.FileRetriever{Path: "testdata/flag-config.yaml"},
FileFormat: "yaml",
Notifiers: []ffclient.NotifierConfig{
&ffclient.WebhookConfig{
PayloadURL: " https://example.com/hook",
Secret: "Secret",
Meta: map[string]string{
"app.name": "my app",
},
},
},
}
0.5.4
to 0.5.5
1.37.20
to 1.38.10
Published by thomaspoignant over 3 years ago