-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigator sending advise requests to user-api #622
Comments
/assign @KPostOffice |
/lifecycle active |
/priority critical-urgent |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
I believe this is still an outstanding request (please correct if not), so |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Is your feature request related to a problem? Please describe.
Recent changes to Kebechet have caused optimizations to only schedule advises when specifically requested, this means that internal triggers scheduling Kebechet will no longer cause user-api requests. We need to move these requests further up the pipeline to investigator so that we can handle new CVE issues.
Describe the solution you'd like
Use Thamos to send authenticated requests to UserAPI directly from investigator
Describe alternatives you've considered
There may be an option for sending advise schedule methods directly, but this requires bypassing caching which exists on user-api. It would also require duplicating the code in user-api which stores the software stacks for later retrieval by adviser.
The text was updated successfully, but these errors were encountered: