Skip to content
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

Open
KPostOffice opened this issue Feb 7, 2022 · 8 comments
Open

Investigator sending advise requests to user-api #622

KPostOffice opened this issue Feb 7, 2022 · 8 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@KPostOffice
Copy link
Member

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.

@KPostOffice KPostOffice added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 7, 2022
@KPostOffice
Copy link
Member Author

/assign @KPostOffice
/life-cycle active

@KPostOffice
Copy link
Member Author

/lifecycle active

@sesheta sesheta added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Feb 7, 2022
@goern
Copy link
Member

goern commented Feb 16, 2022

/priority critical-urgent

@sesheta sesheta added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Feb 16, 2022
@sesheta
Copy link
Member

sesheta commented May 17, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels May 17, 2022
@sesheta
Copy link
Member

sesheta commented Jun 16, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 16, 2022
@codificat
Copy link
Member

I believe this is still an outstanding request (please correct if not), so
/remove-lifecycle rotten

@sesheta sesheta removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 21, 2022
@sesheta
Copy link
Member

sesheta commented Sep 19, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 19, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2022
@harshad16 harshad16 moved this to 🆕 New in Planning Board Oct 7, 2022
@codificat codificat added sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. and removed sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. labels Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Status: 🆕 New
Development

No branches or pull requests

5 participants