[APPPOCTOOL-4] Improve UX of the Kong Manager by using human readable names of routes Created: 02/Feb/24 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | applications-poc-tools |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Dima Tkachenko | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | back-end, epam-eureka, eureka-phase4, need-review | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: | |
| Development Team: | Eureka |
| Description |
|
Kong has a UI tool (Kong Manager) which among other things also displays configured routes:
Currently route's name is formed from the combination of "path + httpMethods + tenant + moduleId + interfaceId" and the result value is hashed: Instead of combining the values and hashing we could try using some more human readable names, like combination of tenant + path + methods The exact format and the content are debatable but at least we can start from the above Example: Route expression: (http.path == "/eholdings/access-types" && http.method == "GET" && http.headers.x_okapi_tenant == "oleksandrkcrestest") Name:
"[diku] GET /eholdings/access-types"
|