{CI} Supress golden gate oracledatabase cred scan

[JaysonTaiMicrosoft]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install azdev required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[Copilot]

🟡 Changes recommended

The companion Golden Gate connection recording contains the same dummy credential but remains unsuppressed.

1 open finding

• Include companion Golden Gate recording in credential suppression · New

What changed in this PR

Updates credential-scan suppressions for Oracle Database Golden Gate test fixtures.

Changes:

• Adds Golden Gate test and deployment recording suppressions.
• Removes the obsolete DB-system recording suppression.

File	Description
scripts/​ci/​credscan/​CredScanSuppressions.json	Updates Oracle Database false-positive paths.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.