Repository navigation
fix(runner): report skipped auto-discovery providers #809
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: projectdiscovery/cloudlist
Length of output: 10454
🏁 Script executed:
Repository: projectdiscovery/cloudlist
Length of output: 15166
🏁 Script executed:
Repository: projectdiscovery/cloudlist
Length of output: 2133
🌐 Web query:
github.com/projectdiscovery/gologger v1.1.73 Fatal implementation💡 Result:
🌐 Web query:
site:pkg.go.dev/github.com/projectdiscovery/gologger/v1.1.73 gologger Fatal exits💡 Result:
Parse
-adbefore legacy config migration.ParseOptionsmigratesconfig.yamlbefore it parses-ad. A rename failure callsgologger.Fatal, which exits the program. Auto-discovery instead usesautoDiscoveryConfig()and does not readprovider-config.yaml. Move the migration after flag parsing and skip it whenoptions.AutoDiscoveryis true.Suggested fix
func ParseOptions() *Options { - // Migrate config to provider config - if fileutil.FileExists(defaultConfigLocation) && !fileutil.FileExists(defaultProviderConfigLocation) { - if _, err := readProviderConfig(defaultConfigLocation); err == nil { - gologger.Info().Msg("Detected old config.yaml file, trying to rename it to provider-config.yaml\n") - if err := os.Rename(defaultConfigLocation, defaultProviderConfigLocation); err != nil { - gologger.Fatal().Msgf("Could not rename existing config (config.yaml) to provider config (provider-config.yaml): %s\n", err) - } else { - gologger.Info().Msg("Renamed config.yaml to provider-config.yaml successfully\n") - } - } - } - options := &Options{} flagSet := goflags.NewFlagSet() @@ _ = flagSet.Parse() + if !options.AutoDiscovery && fileutil.FileExists(defaultConfigLocation) && !fileutil.FileExists(defaultProviderConfigLocation) { + if _, err := readProviderConfig(defaultConfigLocation); err == nil { + gologger.Info().Msg("Detected old config.yaml file, trying to rename it to provider-config.yaml\n") + if err := os.Rename(defaultConfigLocation, defaultProviderConfigLocation); err != nil { + gologger.Fatal().Msgf("Could not rename existing config (config.yaml) to provider config (provider-config.yaml): %s\n", err) + } else { + gologger.Info().Msg("Renamed config.yaml to provider-config.yaml successfully\n") + } + } + } + options.configureOutput()🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skipping: the legacy config.yaml rename predates -ad, only runs when an old config already exists, and migrates the user's own file rather than creating one. ParseOptions reads os.Args and runs the update check, so a CLI-level test is out of proportion here; New covers that -ad never reads the provider config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dogancanbakirThanks for clarifying. The legacy rename is separate from default provider-config creation. I won’t press for a migration change or a CLI-level test here. TheNewtest covers the provider-config read behavior.✏️ Learnings added
You are interacting with an AI system.