[
https://issues.apache.org/jira/browse/CAMEL-26626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-26626:
-------------------------------------
Description:
Part of the move of the Google test-infra to Floci GCP (CAMEL-26622).
The integration test of camel-google-functions ({{GoogleCloudIT}}) is disabled
and needs {{GOOGLE_APPLICATION_CREDENTIALS}} for a real project.
h4. Parked
camel-google-functions calls the Cloud Functions v1 API
({{com.google.cloud.functions.v1.CloudFunctionsServiceClient}}), while Floci
GCP 0.12.0 emulates only the control plane of the v2 API, over REST: its
documentation lists the v1 API as not implemented. So the test cannot run on
Floci GCP until Floci GCP serves the v1 API, or the component moves to the v2
one.
h4. Change, once one of them happens
* Add a local Cloud Functions service on Floci GCP to the Google test-infra.
* Run the management operations against it; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
{{callFunction}} needs a running function, which Floci GCP does not provide.
_Claude Code on behalf of Andrea Cosentino_
was:
Part of the move of the Google test-infra to Floci GCP (CAMEL-26622).
The integration test of camel-google-functions ({{GoogleCloudIT}}) is disabled
and needs {{GOOGLE_APPLICATION_CREDENTIALS}} for a real project.
Floci GCP emulates the Cloud Functions control plane: functions, masked
updates, IAM policies, source upload URLs and long-running operations. It does
not run functions.
h4. Change
* Add a local Cloud Functions service on Floci GCP to the Google test-infra.
* Run the management operations (list, get, create, update, delete,
generateUploadUrl, generateDownloadUrl) against it; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
h4. Not covered
{{callFunction}} needs a running function, which Floci GCP does not provide.
Depends on CAMEL-26622, which adds the Floci GCP container to the Google
test-infra.
_Claude Code on behalf of Andrea Cosentino_
> camel-google-functions - run the integration tests on Floci GCP
> ---------------------------------------------------------------
>
> Key: CAMEL-26626
> URL: https://issues.apache.org/jira/browse/CAMEL-26626
> Project: Camel
> Issue Type: Test
> Components: camel-google-functions
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
>
> Part of the move of the Google test-infra to Floci GCP (CAMEL-26622).
> The integration test of camel-google-functions ({{GoogleCloudIT}}) is
> disabled and needs {{GOOGLE_APPLICATION_CREDENTIALS}} for a real project.
> h4. Parked
> camel-google-functions calls the Cloud Functions v1 API
> ({{com.google.cloud.functions.v1.CloudFunctionsServiceClient}}), while Floci
> GCP 0.12.0 emulates only the control plane of the v2 API, over REST: its
> documentation lists the v1 API as not implemented. So the test cannot run on
> Floci GCP until Floci GCP serves the v1 API, or the component moves to the v2
> one.
> h4. Change, once one of them happens
> * Add a local Cloud Functions service on Floci GCP to the Google test-infra.
> * Run the management operations against it; keep the remote mode.
> * Skip the integration tests on ppc64le and s390x.
> {{callFunction}} needs a running function, which Floci GCP does not provide.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)