[
https://issues.apache.org/jira/browse/CAMEL-26622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-26622:
-------------------------------------
Component/s: camel-test-infra
Description:
The integration test of camel-google-storage ({{ComplexIT}}) runs only with
{{GOOGLE_APPLICATION_CREDENTIALS}} set for a real project.
Floci GCP ([https://github.com/floci-io/floci-gcp], MIT) is the Google Cloud
emulator of the family that the AWS test-infra (since
[#23404|https://github.com/apache/camel/pull/23404]) and the Azure one
(CAMEL-26615) use: one container serves the gRPC and REST APIs of Cloud
Storage, Pub/Sub, Firestore, Secret Manager, BigQuery and more on port 4588. It
emulates Cloud Storage over REST (JSON and XML) and gRPC: buckets, objects,
resumable uploads, ranged downloads, copy and rewrite, versioning, V4 signed
URLs.
h4. Change
* Add a Floci GCP container to a new {{camel-test-infra-google-common}} module,
with the image in {{container.properties}} and a readiness wait. It was planned
in CAMEL-26614, which is parked: Pub/Sub stays on the Cloud SDK emulator for
now.
* Add a {{camel-test-infra-google-storage}} module: a local Cloud Storage
service on Floci GCP, and a remote one for a real project.
* Run the integration test against it; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
* Regenerate the test-infra metadata of the catalog.
_Claude Code on behalf of Andrea Cosentino_
was:
Part of the move of the Google test-infra to Floci GCP (CAMEL-26614).
The integration test of camel-google-storage ({{ComplexIT}}) runs only with
{{GOOGLE_APPLICATION_CREDENTIALS}} set for a real project.
Floci GCP emulates Cloud Storage over REST (JSON and XML) and gRPC: buckets,
objects, resumable uploads, ranged downloads, copy and rewrite, versioning, V4
signed URLs.
h4. Change
* Add a local Cloud Storage service on Floci GCP to the Google test-infra.
* Run the integration tests against it; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
Depends on CAMEL-26614.
_Claude Code on behalf of Andrea Cosentino_
> camel-google-storage - run the integration tests on Floci GCP
> -------------------------------------------------------------
>
> Key: CAMEL-26622
> URL: https://issues.apache.org/jira/browse/CAMEL-26622
> Project: Camel
> Issue Type: Test
> Components: camel-google-storage, camel-test-infra
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
>
> The integration test of camel-google-storage ({{ComplexIT}}) runs only with
> {{GOOGLE_APPLICATION_CREDENTIALS}} set for a real project.
> Floci GCP ([https://github.com/floci-io/floci-gcp], MIT) is the Google Cloud
> emulator of the family that the AWS test-infra (since
> [#23404|https://github.com/apache/camel/pull/23404]) and the Azure one
> (CAMEL-26615) use: one container serves the gRPC and REST APIs of Cloud
> Storage, Pub/Sub, Firestore, Secret Manager, BigQuery and more on port 4588.
> It emulates Cloud Storage over REST (JSON and XML) and gRPC: buckets,
> objects, resumable uploads, ranged downloads, copy and rewrite, versioning,
> V4 signed URLs.
> h4. Change
> * Add a Floci GCP container to a new {{camel-test-infra-google-common}}
> module, with the image in {{container.properties}} and a readiness wait. It
> was planned in CAMEL-26614, which is parked: Pub/Sub stays on the Cloud SDK
> emulator for now.
> * Add a {{camel-test-infra-google-storage}} module: a local Cloud Storage
> service on Floci GCP, and a remote one for a real project.
> * Run the integration test against it; keep the remote mode.
> * Skip the integration tests on ppc64le and s390x.
> * Regenerate the test-infra metadata of the catalog.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
