Apisix-dashboard: show the running step detail info about this API

[juzhiyuan]

Hi @membphis, we have supported the first three steps, as for show the running step detail info about this API, I need to consider this one with @liuxiran. We could close this issue now, let me create a new one at Dashboard to track.

_Originally posted by @juzhiyuan in https://github.com/apache/apisix/issues/1533#issuecomment-789413114_

[nic-chen]

I think we could consider allowing debug routes that status is 0

[liuxiran]

Online debug does not support show the running step detail info about this API currently @juzhiyuan

And if we want to support this feature, the display in FE is not very difficult, we need apis to get all the running steps and the current running step of the request which reaches APISIX, the possibility of the apis may need @nic-chen @spacewander @membphis confirm, thanks

[liuxiran]

I think we could consider allowing debug routes that status is 0

Agree with you @nic-chen , when a route needs debug, it means that this route is still in the test phase, or there are something wrong with it, no matter what reason it is , this route should not publish to users.

[nic-chen]

Online debug does not support show the running step detail info about this API currently @juzhiyuan

And if we want to support this feature, the display in FE is not very difficult, we need apis to get all the running steps and the current running step of the request which reaches APISIX, the possibility of the apis may need @nic-chen @spacewander @membphis confirm, thanks

so we need to expose debug info in APISIX for these detail info

[juzhiyuan]

Here have feedbacks from AISPEECH.

1. the core point is that unpublished routes should only allow test traffic access, no official traffic can be put in.
2. Suggestion: APISIX supports defining global test traffic characteristics, such as defining special fields in the request header to indicate that this is test traffic; route match is done in the full set of routes (including published routes and unpublished routes) when processing test traffic, and after testing and verifying that it meets expectations After testing and verifying that it meets expectations, then publish.

cc @membphis @liuxiran to take a look

[membphis]

Here have feedbacks from AISPEECH.

1. the core point is that unpublished routes should only allow test traffic access, no official traffic can be put in.
2. Suggestion: APISIX supports defining global test traffic characteristics, such as defining special fields in the request header to indicate that this is test traffic; route match is done in the full set of routes (including published routes and unpublished routes) when processing test traffic, and after testing and verifying that it meets expectations After testing and verifying that it meets expectations, then publish.

cc @membphis @liuxiran to take a look

looks good to me. we can implement this feature with a new APISIX plugin.