[SERVER-54663] Update buildloggerv3 route generator to use evg instead of cedar Created: 19/Feb/21 Updated: 29/Oct/23 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Julian Edwards | Assignee: | Julian Edwards |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Evergreen 2021-03-08, Evergreen 2021-03-22 | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
Lobster will need to go through evergreen to access any logs stored in cedar buildlogger (buildloggerv3). The REST route generated for resmoke logging using cedar should use the evergreen route rather than the cedar route. Need to change this. |
| Comments |
| Comment by Githook User [ 15/Mar/21 ] |
|
Author: {'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}Message: |
| Comment by Julian Edwards [ 09/Mar/21 ] |
|
This ticket was updated to remove the route generation and entirely and pass the group id to evergreen via the attach.Results command. |