vsco / dcdr Goto Github PK

The internal version uses our goji-test. We need to extract it from util and release it as well.

The watcher is working but needs some extra tests.

Reported via @fruch in #65

there is some instability in the watch test (in windows it's failing constently)

We are not testing for Windows, an improvement would be to address that.

MIT is fine with me. We should discus though.

Some of this is done but it still needs a ton of work,

Only for back up the configuration? OR you expect the clients to probe it instead of consul?

Having a rest api with similar options as the CLI, can be very helpful:

• building operation web ui for dcdr
• for system testing, when you want to create/delete scopes.

@mikeage might be interested in this one

I was trying Namespace other then dcdr (search in this case) and the dcdr.json looks like that:

{
  "dcdr": {
    "info": {},
    "features": {
      "default": {
        "featue1": true,
        "featue2": 1,
        "feature-a": 0,
        "feature1": true
      },
      "search": {
        "info": null
      },
      "usr": {
        "12345": {
          "featue2": 0.5
        }
      }
    }
  }

Would you consider adding the ability to export/integrate with Prometheus metrics?

Really love the idea of dcdr (almost ideantical to what I wanted for a long time).
would be nice if it had a String Value.

for use case when have enums/state for each scope,
or thing like motd for each user group.