Repository navigation
Scan with nothing to configure - #38
Merged
Merged
Conversation
The all-contexts flag, the all_contexts API field, and the chart's allContexts value are gone. One resolver now serves scan, watch, the serve scheduler, the API trigger, the inbound webhook, and the controller.
A scan now tells the terminal how much of the fleet it observed before it prints a score, and names the three fixes with the most leverage.
With no --db, scans go to a SQLite file under the XDG state directory, so history, trends, and serve work on day two with nothing configured. The path prints once on first use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A bare
fleetsweeper scannow scans every kubeconfig context.--all-contextsis gone from scan, watch, serve, and the init scaffold.--contextsand--groupnarrow the set. One resolver handles the CLI, the serve scheduler, the scan API, and the controller, so an empty API request and a ClusterScan with no contexts both scan everything. Theall_contextsAPI field and chartscheduler.allContextsare removed, and chartscheduler.contextsnow renders.Scans are stored by default in a local SQLite file under the XDG state directory, created 0700/0600 and printed once on first use.
--dbstill overrides it. Commands that required--dbnow use the default store.The terminal summary leads with coverage, then the score or "not graded", then the top three fixes, then cohorts and incidents.
UPGRADING.md has a v0.16.0 section covering each change, and the chart moves to 0.16.0.