Google storage component doesn't work

[jeffgbradley2]

I can't get the simple Google Storage route below to work in Camel K.

<routes id="google-storage-routes" xmlns="http://camel.apache.org/schema/spring">
    <route id="google-cloud-storage-route">
        <from uri="direct:google-cloud-storage-queue" />
        <convertBodyTo type="java.lang.String" />
        <to uri="google-storage:xxxxx" />
    </route>
</routes>

When run in Camel K using the command below, the deploy succeeds but an error is thrown since the google component isn't available.

kamel run google-storage-routes.xml --dev
...
[1] 2021-08-16 18:54:12,534 ERROR [org.apa.cam.qua.mai.CamelMainRuntime] (main) Failed to start application: org.apache.camel.FailedToCreateRouteException: Failed to create route google-cloud-storage-route at: >>> To[google-storage:xxxxxx] <<< in route: Route(google-cloud-storage-route)[From[direct:google-cloud-s... because of No endpoint could be found for: google-storage://xxxxx, please check your classpath contains the needed Camel component jar.

If I add the dependency, the deploy fails.

google-storage git:(master) ✗ kamel run -d camel-google-storage google-storage-routes.xml --dev
integration "google-storage-routes" created
Condition "IntegrationPlatformAvailable" is "True" for Integration google-storage-routes: default/camel-k
Progress: integration "google-storage-routes" in phase Initialization
Progress: integration "google-storage-routes" in phase Building Kit
Integration google-storage-routes in phase "Initialization"
Integration google-storage-routes in phase "Building Kit"
Condition "IntegrationKitAvailable" is "False" for Integration google-storage-routes: creating a new integration kit
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Integration Kit) changed phase to "Build Submitted"
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Build) changed phase to "Scheduling"
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Build) changed phase to "Pending"
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Build) changed phase to "Running"
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Integration Kit) changed phase to "Build Running"
Integration google-storage-routes subresource kit-c4dba6esrkndflf45f8g (Build) changed phase to "Failed"

Why isn't Camel K automatically pulling the google-storage dependency, and why is it failing when the dependency is explicitly added? How should this be updated so that the google-storage component may be used within Camel K?

[johnpoth]

Hi @jeffgbradley2, I can't reproduce using the main branch. What version of camel-k are you using ? The latest release is v1.5.0, Thanks !

[oscerd]

It's main branch now. Il mar 17 ago 2021, 10:52 John Poth ***@***.***> ha scritto:

…

Hi @jeffgbradley2 <https://github.com/jeffgbradley2>, I can't reproduce using the master branch. What version of camel-k are you using ? The latest release is v1.5.0 <https://github.com/apache/camel-k/releases/tag/v1.5.0>, Thanks ! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2576 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABG6XV326QGM743U3RGPDQLT5IPOHANCNFSM5CIKEHUQ> .

[jeffgbradley2]

We've tried with 1.4.0 and 1.5.0, same results.

[squakez]

I've also tested the same with 1.5.0 and it's working as expected. The only thing is that it requires a --build-property quarkus.google.cloud.project-id=test (available in 1.5 only) to startup.

The dependency should be detected automatically. In order to troubleshoot it you can execute kamel describe integration route and see if the dependency was indeed included. Also, you may have a look at the camel-k-operator pod log in order to check problems during the assembly phase. Finally, you may check the Build that is in charge to create a Kit via k describe builds kit-c4ec3jk3k6d8tsit3bvg

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!