Upstreams from store

[fri0z]

I added get_upstreams and set_upstreams to the store and wrote a simple implementation for MemoryStore and RedisStore and one test.

The next step is to implement the use of these methods to get upstreams.

Am I moving in the right direction?

[fri0z]

Oh, and why does this error occur? "all fields have the same prefix: inner"

[fri0z]

@luizfonseca During the development process, a question arose. Or maybe we will store in redis not only the vector of RouteUpstream structures, but the entire Route structure?

[luizfonseca]

@fri0z

Am I moving in the right direction?
Yes! It's always tough to test everything, but it's how I'd move too.

During the development process, a question arose. Or maybe we will store in redis not only the vector of RouteUpstream structures, but the entire Route structure?

it's likely that we might need to have a pattern like:

| key                  | routes                              |
| upstream:example.com | <all routes configuration in JSON?> |
| cert:example.com     | ----------------------------------- |

Downside is that it might make hard to eventually update those as we would need to patch the JSON (I plan to allow changes via an admin API in the future)

[fri0z]

@luizfonseca I suggest using the proksi:route:{domain} and store json in it in a format similar to the Route structure from config.

This will be more convenient during the subsequent implementation of the REST API. But for this you will need to change the RouteStoreContainer.

[luizfonseca]

Ah yes, that's the same line of thought, basically all upstreams injected into => proksi:route:<domain>.

I can check what needs to be done in the RouteStoreContainer

[fri0z]

@luizfonseca let's update the key in the specification documentation?