fix: resolve ZAP baseline scan report filename mismatch

[HarshitVerma109]

Proposed change

Resolves #3183

This PR fixes the CI/CD pipeline failure in the ZAP Baseline Scan jobs. The zaproxy/action-baseline action expects the HTML report to be named report_html.html by default, but the workflow configuration was overriding this with -r zap-report.html in cmd_options, causing a file not found error.

Changes made:

• Remove -r zap-report.html from cmd_options to use default filename
• Update artifact upload path to report_html.html
• Fixes both staging and production scan jobs
• Resolves issue where action expected report_html.html but got zap-report.html

Files modified:

• .github/workflows/run-ci-cd.yaml

Checklist

• Required: I read and followed the contributing guidelines
• Required: I ran make check-test locally and all tests passed
• I used AI for code, documentation, or tests in this PR

[coderabbitai]

Walkthrough

Two ZAP baseline scan CI jobs in the GitHub Actions workflow were reconfigured. The scan command flag -r zap-report.html was removed, leaving only -a, and the artifact upload path changed from zap-report.html to report_html.html. Configuration-only adjustments with no logic modifications.

Changes

Cohort / File(s)	Summary
ZAP Baseline Scan Configuration ​.github/workflows/run-ci-cd.yaml	Removed -r zap-report.html command flag (now uses -a only) and updated artifact path from zap-report.html to report_html.html in two CI jobs

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• ci: add ZAP Baseline Scan to CI/CD pipeline #3172 — Also modifies the ZAP Baseline Scan job configuration in the same workflow file with similar command and artifact path adjustments

Suggested labels

ci

Suggested reviewers

• arkid15r
• kasya

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing a filename mismatch in ZAP baseline scan reports, which is the core issue addressed in the PR.
Linked Issues check	✅ Passed	The PR successfully addresses the primary objective from issue #3183 by fixing the CI/CD workflow failure caused by the ZAP baseline scan job filename mismatch between expected and configured report names.
Out of Scope Changes check	✅ Passed	All changes are narrowly scoped to fixing the ZAP baseline scan filename issue in the CI/CD workflow; no unrelated modifications to other functionality or systems are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The PR description clearly explains the issue, the specific changes made, and how they resolve the ZAP baseline scan report filename mismatch.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[HarshitVerma109]

@arkid15r
Please review

[arkid15r]

Closing in favor of #3198