e2e: GCP export to e2e using fake-gcs-server #416
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit integrates GCP export verification into the test_vapi e2e test using a local GCS emulator (fake-gcs-server) to avoid requiring real GCP credentials in CI/CD. Changes: - Add fake-gcs-server deployment and service manifests (fake-gcs-server seems to be a reliable GCP emlator) - Configure rapidast-vapi to export results to GCS emulator - Implement verify_gcs_export_succeeded() function to validate exports - Deploy fake-gcs-server in test_vapi before running scan Additional notes: - currently verify_gcs_export_succeeded() only verifies that at least 1 file was uploaded. Future improvement could verify its content The fake-gcs-server emulator runs at http://fake-gcs-server:4443 and provides a local GCS-compatible API that the google-cloud-storage Python library automatically uses when STORAGE_EMULATOR_HOST is set. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
cedricbu
force-pushed
the
e2e-gcp-export
branch
from
73efbde to
1034224
Compare
The readiness probe was failing because Kubernetes defaults to HTTPS for httpGet probes, but fake-gcs-server is configured to use HTTP. This fix explicitly sets scheme: HTTP in the readiness probe to match the server configuration.
Collaborator
|
I'm wondering if it would be simpler to instead have a test bucket in GCS and push test results there? That might also be closer to reality, I'm not sure how similar fake-gcs-server is to the real thing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit integrates GCP export verification into the test_vapi e2e test using a local GCS emulator (fake-gcs-server) to avoid requiring real GCP credentials in CI/CD.
Changes:
Additional notes:
The fake-gcs-server emulator runs at http://fake-gcs-server:4443 and provides a local GCS-compatible API that the google-cloud-storage Python library automatically uses when STORAGE_EMULATOR_HOST is set.
🤖 Generated with Claude Code