-
Notifications
You must be signed in to change notification settings - Fork 28
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
Merge autopilot into bus #1640
Comments
@ChrisSchinnerl what's the reasoning behind scoring hosts in the scan endpoint if the autopilot is enabled? Do we still want to score a host when we perform checks on hosts in the maintenance loop? Do we want to scan more frequently? The reason I'm asking is the |
The idea was that when you manually scan a host via the UI, you immediately get feedback as a user and don't need to wait for the maintenance to run. So we'd still have the regular maintenance but additionally a scan would also perform some checks. That said I think we can hold off on that part until v2.1 or v3.0. We might not want to continue having a |
…1767) This PR restructures the autopilot in a way that makes it easier to eventually move the autopilot and make it a subsystem of the bus. This focuses mostly on the contractor; the next step would be to fix the catch-22 we have while constructing the migrator. Getting these out of the way should make it a lot easier to merge the autopilot into the bus. I considered moving pruning to the contractor, but I'm still 50–50 on that. A quick-and-dirty way to merge the autopilot is to keep using a bus client, but I figured it's a good opportunity to clean things up a bit because it's grown unwieldy. Related to #1640.
The autopilot API should be merged into the bus. That means
The text was updated successfully, but these errors were encountered: