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

hide provider-config not exist error and auto create it #425

Closed
tarunKoyalwar opened this issue Mar 1, 2024 · 0 comments · Fixed by #431
Closed

hide provider-config not exist error and auto create it #425

tarunKoyalwar opened this issue Mar 1, 2024 · 0 comments · Fixed by #431
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Milestone

Comments

@tarunKoyalwar
Copy link
Member

uncover version:

main | library

Proposed Changes

  • when uncover is used as library in nuclei it logs error saying that provider config does not exist. instead of that it should just create the corresponding file instead
[ERR] failed to load provider keys got [uncover:RUNTIME] provider config file .uncover-config/uncover/provider-config.yaml does not exist
@tarunKoyalwar tarunKoyalwar added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Mar 1, 2024
@RamanaReddy0M RamanaReddy0M linked a pull request Mar 7, 2024 that will close this issue
@tarunKoyalwar tarunKoyalwar added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Mar 10, 2024
@ehsandeep ehsandeep added this to the v1.0.8 milestone May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants