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

Custom Filters cannot be passed in from the command line #202

Open
1 of 2 tasks
a-weiss-programmer opened this issue Apr 3, 2024 · 0 comments
Open
1 of 2 tasks

Comments

@a-weiss-programmer
Copy link

  • I'm submitting a ...

    • bug report
    • feature request
  • What is the current behavior?
    Adding a custom filter by file when doing a command line scan is not working. When trying to pass a custom filter as described in the document, a command line usage error comes back saying "detect-secrets scan: error: argument -f/--filter: Did not specify function name for imported file."

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. Install bc-detect-secrets
  2. Create a custom_filter.py script with the given filter in the documentation
  3. Invoke the command below the example script provided in the filter documentation
    ax8YXP0dQN
  • What is the expected behavior?
    The expected behavior is that the filter would be picked up properly. This functionality works when invoking detect secrets from a separate python program.

  • What is the motivation / use case for changing the behavior?
    Allows for proper usage of the command line behavior provided

  • Please tell us about your environment:

    • detect-secrets Version: 1.5.5
    • Python Version: 3.11.8
    • OS Version: Ubuntu 22.04.4 LTS (Windows Subsystem for Linux)
    • File type (if applicable):
  • Other information
    This is most likely an issue with urllib parsing of the file in the filters usage file, as urlparse returns a ParseResult where the netloc property is populated with the filepath instead of the path property, since the scheme is file based.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant