* #296 renamed configuration.json to ocelot.json in preparation
* removed things we dont need for tests
* another file we dont need
* removed some async we dont need
* refactoring to consolidate configuration code
* removed another pointless abstraction
* #296 started writing merge code
* #296 coming up with ideas for this config merging
* #296 still hacking this idea around
* #296 will now do a crappy merge on the configuration
* #296 change so tests pass on windows
* removed file
* updated package
* updated package
* updated package
* updated package
* updated package
* updated package
* updated package
* all packages updated
* #295 can add token to service provider config and this will be used by consul clients to get services and configuration
* #295 wait longer for this test
* squash SA1649 warnings (file/type name mismatch)
* squash SA1127 warnings (generic constraint on own line)
* squash SA1507 warnings (multiple blank lines)
* squash package analysis warnings re: summary text
It's not actually possible to provide a summary right now as per
https://github.com/NuGet/Home/issues/4587
* squash missing castle.core reference warning
* squash obsolete method warnings re: AddOcelotBaseUrl
* initial commits around using any id servers
* add your own id server for admin area
* lots of refactoring, now instead of injecting IWebHostBuilder we just set the Ocelot base url as a configuration extension method..this means people can pass it in on the command line aswell as hardcode which is OK I guess, also can now use your own IdentityServer to authenticate admin area
* updated docs for #231
* some tests that hopefully bump up coverage
* feat： use Https://github.com/ButterflyAPM to monitor each API request monitoring metrics
* feat: using DiagnosticSource and Butterfly.OpenTracing
* refactor：refactor Ocelot tracing， merge code into OcelotDiagnosticListener
* refactor: move OcelotHttpTracingHandler to Requester
* fix： Requester\HttpClientBuilder.cs(10,14): error CS0234: The type or namespace name 'Tracing' does not exist in the namespace
* feat: add test should_set_up_tracing
* feat : Remove extraneous code
* feat: remove unused DiagnosticSource diagnostic
* fix : test UseTracing
* add test should_call_scoped_data_repository_QosProviderError
* add test should_return_any_errors
* add test HttpClientHttpRequesterTest
* it should keep it can not be deleted
* hacked together load balancing reroutes in fileconfig
* some renaming and refactoring
* more renames
* hacked away the old config json
* test for issue 213
* renamed key
* dont share ports
* oops
* updated docs
* mvoed docs around
* port being used
* hacking around to work out why logging and request id isnt working
* pass request id into logger so it can be structured, removed a bunch of debug logging we dont need because diagnostic trace gets it
* changed config dependency
* always have tracing available
* made it so we dont need to pass config into services.AddOcelot anymore with .net core 2.0
* add test
* lots of changes relating to logging and request ids, also updated documentation
* fixed failing test i missed
* brought in rafty
* moved raft classes into Ocelot and deleted from int project
* started to set up rafty in Ocelot
* RAFTY INSIDE OCELOT...WOOT
* more work adding rafty...just need to get auth working now
* rudimentary authenticated raft requests working
* asyn await stuff
* hacked rafty into the fileconfigurationcontroller...everything seems to be working roughly but I have a lot of refactoring to do
* updated to latest rafty that doesnt need an id
* hacky but all tests passing
* changed admin area set up to use builder not configuration.json, changed admin area auth to use client credentials
* missing code coverage
* ignore raft sectionf for code coverage
* ignore raft sectionf for code coverage
* back to normal filters
* try exclude attr
* missed these
* moved client secret to builder for authentication and updated docs
* lock to try and fix error accessing identity server created temprsa file on build server
* updated postman scripts and changed Ocelot to not always use type handling as this looked crap when manually accessing the configuration endpoint
* added rafty docs
* changes I missed
* added serialisation code we need for rafty to process commands when they proxy to leader
* moved controllers into their feature slices
