Skip to content

ROX-33574: Don't forget to configure scanner pull secrets#19451

Open
rhacs-bot wants to merge 1 commit intorelease-4.9from
backport-19383-to-release-4.9
Open

ROX-33574: Don't forget to configure scanner pull secrets#19451
rhacs-bot wants to merge 1 commit intorelease-4.9from
backport-19383-to-release-4.9

Conversation

@rhacs-bot
Copy link
Contributor

Backport 1331603 from #19383.

@gitguardian
Copy link

gitguardian bot commented Mar 17, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
28322140 Triggered Username Password 2ae20a4 pkg/helm/charts/tests/securedclusterservices/testdata/helmtest/image-pull-secrets.test.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@github-actions github-actions bot added area/helm backport PR to backport changes from master to release branch labels Mar 17, 2026
@rhacs-bot
Copy link
Contributor Author

Images are ready for the commit at 2ae20a4.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.9.4-1-g2ae20a4384.

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.87%. Comparing base (b03e71c) to head (2ae20a4).

Additional details and impacted files
@@               Coverage Diff               @@
##           release-4.9   #19451      +/-   ##
===============================================
- Coverage        48.87%   48.87%   -0.01%     
===============================================
  Files             2719     2719              
  Lines           202915   202915              
===============================================
- Hits             99181    99174       -7     
- Misses           95965    95972       +7     
  Partials          7769     7769              
Flag Coverage Δ
go-unit-tests 48.87% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Contributor

/konflux-retest main-on-push

@github-actions
Copy link
Contributor

/konflux-retest operator-bundle-on-push

@mclasmeier
Copy link
Contributor

/retest

@github-actions
Copy link
Contributor

/konflux-retest main-on-push

@github-actions
Copy link
Contributor

/konflux-retest operator-bundle-on-push

@openshift-ci
Copy link

openshift-ci bot commented Mar 17, 2026

@rhacs-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/ocp-dev-preview-scanner-v4-install-tests 2ae20a4 link false /test ocp-dev-preview-scanner-v4-install-tests
ci/prow/ocp-dev-preview-qa-e2e-tests 2ae20a4 link false /test ocp-dev-preview-qa-e2e-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/helm backport PR to backport changes from master to release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants