fix: prevent logging sensitive API key data in test

[jhamon]

Summary

Fixed security vulnerability where API key response objects containing sensitive data were being logged in clear text in test files.

Changes

• Modified tests/integration/rest_sync/admin/test_api_key.py to log only non-sensitive API key IDs instead of full response objects
• This prevents exposure of sensitive data (passwords/API key values) in logs

Security Impact

• Resolves code scanning alert Update Code #72: https://github.com/pinecone-io/pinecone-python-client/security/code-scanning/72
• Addresses CWE-312 (Cleartext Storage of Sensitive Information)
• Addresses CWE-532 (Insertion of Sensitive Information into Log File)
• Security severity: High

Testing

• Existing tests continue to pass
• Pre-commit hooks passed

Made with Cursor

---

Note

Low Risk
Low risk test-only change that reduces exposure of sensitive API key material in logs; no runtime behavior is affected.

Overview
Updates the admin API key integration test to stop logging full API key response objects and instead log only non-sensitive identifiers (the key id) when fetching via fetch/get aliases, preventing accidental leakage of API key values in test logs.

^{Written by Cursor Bugbot for commit a5cf44f. This will update automatically on new commits. Configure here.}