This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Implement functinality to patch system based on recommended actions #257
Labels
story-points-20
20 Story Points
Comments
This was referenced Jan 14, 2020
We want to demo this for an investor, so let's take some shortcuts to get the alpha version of this working. Here are some shortcuts:
Outstanding tasks for MVP after #263:
|
MVP is done Sprint 16. We've received great feedback on this. Now we need to revisit the original scope in Sprint 17. |
We need to resume work on this. As next steps, I want to do the following:
Next sprint
|
13 complexity points |
20 |
This was referenced Mar 20, 2020
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We want to make it easy for users to patch their systems by having a simple one-liner to do this. Unfortunately, this can become somewhat troublesome when you have different configurations across the fleet.
As such, we want to extend the CLI for easier patching of packages.
We want to keep this as dynamic as possible. Hence, we could do something similar to
wott-agent patch $ID
, where $ID is the issue from the backend. This could either be CVE or a change.Here's an example of how I envision a run to look like:
Example of patching a service.
Example of upgrading packages/patching for CVE.
Considerations:
The text was updated successfully, but these errors were encountered: