First of all: thanks for working on this project and making it accessible to us!

Context

We are starting the unleash server in the same process as our backend server, using unleash.start().
When we receive a SIGINT or SIGTERm, we want to shutdown cleanly so that node exits on it's own because of an empty event loop.

What we tried

Our current attempt to do this boils down t

And, ideally, a configurable list of annotations denoting generated source or AST structures.

See #105 for the kind of issue this seeks to avoid, and the limitations of this fix.

As we are constantly upgrading Flagr server, the client SDKs may experience unexpected changes from the server side. The integration tests should better include these SDKs instead of just simple CURL tests.

Specifically, we want to cover

• https://github.com/checkr/jsflagr
• https://github.com/checkr/rbflagr
• https://github.com/checkr/pyflagr
• https://github.com/checkr/goflagr

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

I've created a provisioning script and a client wrapper for the Bullet Train API which throws an exception when attempting to parse the response from /api/v1/users/init/ as it seems to only return a text body of, "ADMIN USER CREATED".

Ideally, when the Accept header is set to application/json, the API could return either a 201 Created response with no body or the same message as a JSON