Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google PubSub Extension is not working in camel-k #2796

Closed
oscerd opened this issue Jun 16, 2021 · 4 comments
Closed

Google PubSub Extension is not working in camel-k #2796

oscerd opened this issue Jun 16, 2021 · 4 comments
Milestone

Comments

@oscerd
Copy link
Contributor

oscerd commented Jun 16, 2021

I was testing a development kamelet for google pubsub source. The projectId is set in the Kamelet, but I'm getting:

[1] Jun 16, 2021 10:35:32 AM io.quarkus.config
[1] WARN: Unrecognized configuration key "%s" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
[1] Jun 16, 2021 10:35:32 AM io.quarkus.config
[1] WARN: Unrecognized configuration key "%s" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
[1] One or more configuration errors have prevented the application from starting. The errors are:
[1]   - SRCFG00014: The config property quarkus.google.cloud.project-id is required but it could not be found in any config source
[1]   - SRCFG00014: The config property quarkus.google.cloud.project-id is required but it could not be found in any config source
  flow:
    from:
      uri: "google-pubsub:{{projectId}}:{{subscriptionName}}"
      parameters:
        .
        .
        .
        .
      steps:
      - to: "kamelet:sink"

The projectId is set at kamelet level and should be set a path level in the route.

@oscerd
Copy link
Contributor Author

oscerd commented Jun 16, 2021

This is with camel-k 1.5.0-SNAPSHOT, camel-k-runtime 1.9.0-SNAPSHOT base on 2.0.0-M2

@jamesnetherton
Copy link
Contributor

Relates to #2858.

@jamesnetherton
Copy link
Contributor

This should be fixed since CQ 2.2.0. @oscerd maybe you can confirm?

@oscerd
Copy link
Contributor Author

oscerd commented Sep 17, 2021

Yes, it works fine with 2.2.0 :-)

Thanks for helping

@ppalaga ppalaga added this to the 2.2.0 milestone Sep 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants