Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19449

Include branch name in the secret scanning

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Secret Scanning
    • None
    • 0
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The current view of the report for the found issue includes the commit ID but doesn't include the branch name.

      # When a file containing secrets is found:
      Node ID: 67a19601-3e87-405e-8951-6b0be58caf71
      Method: System
      Commit id: db53836ac53694d4a12dc2a84e56f46ac8cf01d4
      Initiating user: kevin
      Line: null
      Path: more.jks
      Rule id: Java keystore file
      More affected objects: db53836ac53 kevin
      ----
      ## When a secret is found within a file:
      ...
      Line: 1
      Path: env
      Rule id: Basic auth
      More affected objects: 0a1fea57765 kevin
      

      Even though the report is designed to show objects without regard to whether they belong to a branch or are dangling, it would be good to include the branch name in the report whenever possible.

              Unassigned Unassigned
              ashaleev Anton Shaleev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: