[SERVER-79852] Establish mechanism for managing API key (for remote execution) Created: 08/Aug/23 Updated: 18/Jan/24 Resolved: 18/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Steve Gross | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Build |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Build
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When we adopt a 3P service for remote execution, there will be an API key that needs to be managed. We should research and identify a preferred solution. 1. Make sure to remove related todos in evergreen yml and shell scripts. |
| Comments |
| Comment by Zack Winter [ 18/Jan/24 ] |
|
Marking this as implemented since we have engflow API management setup |