Igor Stoyanov Atlassian Team

Hi @John Alberts . Here i provided configuration: - pipe: docker://bitbucketpipelines/git-secrets-scan:3.1.0 variables: DEBUG: "true" GITLEAKS_EXTRA_ARGS: - "--verbose" - "--redact=100" - "--max-decode-depth=3" And here is the output: Try to add DEBUG to see gitleaks generated command. Regards, Igor

Hi @Max H. Please, provide us with bitbucket-pipelines.yml configuration file to properly understand your case. Regards, Igor

Hi @maciek skorczewski . Please, check this answer. Regards, Igor

Hi @Casper Rademaker . Your arguments was not passed correctly, because it is required to use them in a different way: variables: DEBUG: "true" GITLEAKS_EXTRA_ARGS: - "--redact=100" - "--max-decode-depth=3" also you could skip --verbose since this flag added automatically with by DEBUG: "true" I tried to reproduce your…

Hi @Casper Rademaker . New version of the pipe with correct links available. Example: ```The pipeline does not seem to find any leaked secrets when triggered manually, rather than from a pull request.``` -- could not reproduce this. Regards, Igor

Hi @Rik Overvelde . Thanks for your suggestion. We will investigate this and notify you when new pipe version will become available. Regards, Igor

Hi @Casper Rademaker . Thanks for your suggestion. Currently under file section in annotation is the same string you could see in the gitleaks report annotation. Your example from gitleaks: Finding: AUTH_CLIENT_ID=xxx...File: proxy/.env.development Bu the UI in the Bitbucket Pipelines redirect to the source file by path…

@Adam Lofthouse-Hill hi. Thanks for your question. Multi-platform build feature is not officially supported yet. Regards, Igor

Hi @Haley Loyd . Thanks for your question. Unfortunately, your example will not work. But you could try the next: Put or save the files you want to upload into some folder `upload_folder` and then try this example: script: - pipe: atlassian/azure-storage-deploy:2.5.1 variables: SOURCE: 'upload_folder/*'…

@Suryendu Bhattacharyya hi. New version of pipe released with a support of the Workflows. Regards, Igor

@Anders Ervik . Thanks for the additional details. Our team will investigate this. Regards, Igor

@Anders Ervik Hi. Thanks for your question. Please, next time create your own topic, for your own issue. Try to update the pipe version to 0.4.0 and see if a problem still happen. Regards, Igor

Hi @Abdelmassih Abdelmassih. Please, check the docs. You should add paths under [allowlist] section in gitleaks.toml file. Example: # This is a global allowlist which has a higher order of precedence than rule-specific allowlists.# If a commit listed in the `commits` field below is encountered then that commit will be…

Hi @Ahmad Yazbek . Please, check the docs. You should add paths under [allowlist] section. Example: # This is a global allowlist which has a higher order of precedence than rule-specific allowlists.# If a commit listed in the `commits` field below is encountered then that commit will be skipped and no# secrets will be…

@Yashvit hi. Unfortunately, i do not know exact response for your question, but maybe this article could help you to configure Azure Application Gateway. Regards, Igor

@Sachin Kaushik Hi. Check the file here: How to use artifacts Regards, Igor

Hi @sachin.patil . It would be nice if you provide your bitbucket pipelines configuration yml and log outputs here yo understand your issue. Regards, Igor

Hi @Duy Nguyen . From what i see, you use wrong configuration: - pipe: atlassian/aws-cloudfront-invalidate:0.10.1 variables: AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION AWS_OIDC_ROLE_ARN: $AWS_ARN DISTRIBUTION_ID: $DISTRIBUTION_ID PATH: '/*' You use PATH, but pipe expect PATHS script: - pipe:…

If you’d like to suggest a pipe to be improved with your feature, please, find the appropriate ticket in the list of existing tickets , vote for them or create a new suggestion request with type Suggestion and Component: Pipelines - Pipes.

Hi @Duy Nguyen . Thanks for your question. Please, provide more details: * your bitbucket-pipelines.yml configuration file (do not expose any secrets) * your detailed log output from pipelines Regards, Igor

Hi @Nitzan Horovitz . Thanks for your question. Currently there is no such option. Regards, Igor

@Suryendu Bhattacharyya thanks for your feedback. Our team will investigate this Regards, Igor

I still see that webhook required for workflow. Regards, Igor

@Suryendu Bhattacharyya hi. According this page isn't it just a replace old webhook url with new webhook url? So you can paste your updated url and that's all? Regards, Igor

Hi @Thomas Einwaller . Here below what worked for me when i tested this feature. You can get fingerprint from report by clicking on the annotation: And then add this fingerprint to the `.gitleaksignore` file: 6e6ff7de96fddd15482674fbe74a2c74d6c4ab90:test/test.json:aws-access-token:1 Hope it helps. Regards, Igor

@Sachin Kaushik you could try https://regex101.com/ and see that selected pattern is not match with content of the appSettings.json. Also, i think, you could ask here about your case. Regards, Igor

Hi @Sachin Kaushik . Thanks for your feedback. This pipe is based on gitleaks tool. I also tested your case with using gitleaks: appSettings.json { "ConnectionStrings": { "TestConn": "Data Source=my-test-db;Password=AKIAKEGEYJSDOHQYTEST;Initial Catalog=MyCat;Integrated Security=False;MultiSubnetFailover=true" } } And…

Hi @Sachin Kaushik. Thanks for your question. First of all try to update git-secrets-scan pipe to the latest version, so the reports feature will be enabled in this pipe. I suggest to try basic example so your full repository will be scanned by the tool. script: - pipe: atlassian/git-secrets-scan:3.0.0 In case you want…

Hi @Julien HENRY , @Fletcher, Andrew . Our team released new version of the pipe, where this command git config --global --add safe.directory /opt/atlassian/pipelines/agent/build was added to git-commit.sh file. @Fletcher, Andrew thank you for your investigation and solution. Could you please provide feedback about does…

@remmerci1 hi. According this page isn't it just a replace old webhook url with new webhook url? So you can paste your updated url and that's all? Regards, Igor