add priority order for API routing rules

[ahmadnassri]

currently there's no clear order for which routes are executed first (specifically when using request_path) a priority / order property will determine the order in which to check for matching routes.

[thibaultcha]

The order is clear and described here. Priority with path is already in #369.

[ahmadnassri]

#369 should be one ticket (per the title), the regex one another ticket and now this ... doubt they should / could be all done together.

[thibaultcha]

Its goal is simply to group the future requirements for path improvements instead of spreading them over 3 different issues. Title can be updated and check-list added.

[driverpt]

It would be nice to have an extra implicit parameter when activating the plugin for a certain API, like config.order=2 as an example, in which the default adds to the tail.

e.g.:

curl -X POST http://kong:8001/apis/{api}/plugins \
    --data "name=oauth2" \
    --data "order=2" \ 
    --data "config.scopes=email,phone,address" \
    --data "config.mandatory_scope=true"

This would cause to add oauth2 plugin to the Number 2 position in the Execution Order.

If there would be 3 plugins registered, that would mean that the positions 2 and 3 would be pushed to 3 and 4.

What do you think @thibaultcha

[djMax]

It would seem to be easier to just make the priority come from config with a default. But that's not enough, because the plugin also needs to know that it should "let requests go" even without auth. We did some of this in our fork, but not in a general way. https://github.com/Mashape/kong/compare/release/0.9.2...gas-buddy:js_next?expand=1#diff-29de4a819d2ea94f4d6f15ab1d280c72R450

[thibaultcha]

Closing this since the new router defines its own priorities and those are documented in the new router guide:

https://getkong.org/docs/0.10.x/proxy/