Share condition registry & context among threads.

[kadams54]

Turns out some things need to be shared among the threads. To avoid race conditions, these variables should only be populated at server startup; after that, they should be read-only.

[kadams54]

QA

Dependencies have changed, so fire up a virtualenv and run pip install -r requirements.txt before starting. You should see Bottle and paste install.

1. Startup the included server (which is now multi-threaded paste, wrapped by Bottle) by running python example/server.py.
2. At this point you should be able to hit http://localhost:8080 and see a message about whether the example switch is active or not.
3. Open a new tab to Switchboard admin, at http://localhost:8080/_switchboard/.
4. Verify that you can:
   • Add a switch
   • Delete a switch
   • Edit a switch
   • View switch history
   • Change the switch status (with expected results on the switch output displayed at the root)
   • Add/remove conditions from a switch (again, with expected results on the switch output)

[jrwren]

The user parameter looks unused and untested.

[kadams54]

Yeah, honestly, this (passing user and request into configure) is a hack right now, until I can code up a more robust API for defining a context (i.e. the data that a switch has to work with to determine if it should be active). Internally, user (assigned to context['user']) is only used when versioning a switch. Externally, it can be used (as we do) by custom conditions to turn switches on/off for certain users, groups, permissions, etc.

[jrwren]

👍

[hatched]

👍 Will QA

[hatched]

QA OK!

[hatched]

Not part of this branch but it would be nice if the action icons beside the switch names were bigger with some padding between them.

[kadams54]

Thanks all!

@hatched #14