medigo / laika Goto Github PK

View Code? Open in Web Editor NEW

37.0 37.0 17.0 11.99 MB

:dog: A feature flag service

License: MIT License

Makefile 1.08% Go 58.10% HTML 0.38% JavaScript 28.71% Shell 2.24% CSS 8.45% Dockerfile 1.05%

feature-flags feature-toggles go

laika's People

Contributors

Stargazers

Watchers

Forkers

mbernardes ssimono alexyans frauleingela christophstrasen aechsten gophersgang eggman64 ethanfrogers matchs utsavtiwary04 d-buettner peterzernia jo-ie fincompare stewartm83 isabella232

laika's Issues

Features could be partially active

The flag state could be more complex than on or off. It would be useful to enable a flag only for some percentage of the user base.

Use cases:

A/B Testing
Gradually rollout a feature

Web UI broken on Firefox

When accessing Laika web UI with Firefox, I cannot edit a feature. When clicking on a feature the detail page doesn't open at all

I notice a javacript error in the console: TypeError: e.path is undefined each time I try to open a feature.

Firefox 47 - Linux Mint 18

Unintuitive environments ordering in UI

The order of environment in the UI is Dev, Prod, Test which doesn't match the usual workflow. It is error-prone and could lead to unintentional flag switch on production

Replace package satori/go.uuid

This issue has been opened automaticaly because we think you are using satori/uuid in your code. Unfortunately, satori/uuid has a critical defect where it doesn't generate random UUIDV4s satori/go.uuid#73 and should be replaced as the maintainer has been unresponsive for 5 months with the bug still open. Alternative packages you should consider: https://github.com/google/uuid https://github.com/pborman/uuid

Feat: Add optional comment upon toggle action

I as a delivery-manager or ops-conscious user
In order to allow everyone to better understand the current state of code behind a feature
I would like to provide a comment as to why I toggled a flag on or off

Acceptance-Criteria:

I can add a comment when I toggle a flag
I am not forced to add a comment
I don't need to spend an extra click if I don't want to comment
comments are exposed via the existing webhook event so that downstream systems might use it
comments are saved alongside the toggle history
comments are part of the toggle history API

Feature: Tags for flags

I as a busy product manager in order to easier manage the features of a particular software in my organisation's portfolio, I want to add tags and see tags in the UI.

Acceptance Criteria:

arbitrary number of tags can be added to a flag via the
All added tags are shown on the respective flags in the UI
Bonus: Clicking on a tag filters the list to include only flags with that tag (there is a way to disable the filter)

Add dedicated API for clients

Clients querying the flag configuration currently use the same API end point as the front end. This is fairly wasteful as clients only require a small subset of all data (boolean value for all flags in a given environment).

Allow adding a prexfix to all the routes

As a operator of Laika I want to be able to configure a prefix to be added on all routes so I can deploy it under a load balancer that isn't able to route on domains like AWS ALB

Acceptance Criteria

It is possible to configure a prefix via an environment variable
The front-side routing accepts the confgured prefix
The server-side routing accepts the configured prefix

Split front-end and API into different projects.

As as a user of Laika, I would like to worry only about the API and let my team implement their own interface.

Also for the project it would allow a better separation of responsibilities and decoupling between UI and API.

Simple auth-less endpoint for querying feature status

Motivation - User facing interfaces, at times, need to check the status of a feature (in a particular environment) and then render accordingly. This calls for a need to expose a limited purpose, no-auth api which returns a boolean value on being invoked with the feature name and the environment as the parameters.

Suggestion The api should simply return false on bad request/unknown feature name to avoid exposing any information about the API's behaviour beyond necessary.

Potential pitfalls Although it doesn't expose any sensitive information, the API not being behind auth can pose security challenges.

Tag new version

Given this app has already a couple of versions tagged, would it be possible to tag a new one to milestone the progress made in ~2 years?

Thanks.

No error if address already in use

Reproduce: listen on port 8000 with something, then start Laika on port 8000.

Expected: Laika fails to start and says something like address is already in use.

Actual: Laika claims to be running on port 8000 as usual but in fact is not running because it couldn't allocate the port.

Provide last toggled at timestamp for each feature flag

{
   "name":"amazing_feature",
   "created_at":"2018-03-16T13:38:19Z",
   "status":{
      "env1":true,
      "env2":false
   },
   "feature_status":[
      {
         "name":"env1",
         "status":false,
         "toggled_at":"2018-03-16T13:39:19Z"
      },
      {
         "name":"env2",
         "status":true,
         "toggled_at":"2018-03-16T13:39:19Z"
      }
   ]
}

Show feature log history

It would be nice to see what happened to a feature at a certain moment in time.
On a feature page there could be a log section with the date, user and event of what happened.

E.g.:

2017/07/10 19:22:04 - Mateus - Disabled feature link-buttons-on-top
2017/07/01 14:02:07 - Mateus - Enable feature link-buttons-on-top
2017/07/01 14:01:18 - Mateus - Created feature link-buttons-on-top

Optimize front-end for display on mobile devices

As an administrator I wan't to be able to manage feature flags on the go, in order to react to critical issues in production code.

The current front-end doesn't provide a sufficient UI for mobile usage, since it's only the desktop version scaled into the view port.

We should offer an optimized version of the UI for mobile usage.