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

Kamelets: configuration does not seem to cascade to the integration #2396

Closed
orpiske opened this issue Jun 11, 2021 · 5 comments
Closed

Kamelets: configuration does not seem to cascade to the integration #2396

orpiske opened this issue Jun 11, 2021 · 5 comments
Milestone

Comments

@orpiske
Copy link
Contributor

orpiske commented Jun 11, 2021

I have a kamelet binding defined as below. It includes a section for configuring a property on the integration but it does not seem to cascade to the integration:

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jms-source-binding
spec:
  integration:
    configuration:
      - type: property
        value: "quarkus.log.level=DEBUG"
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: jms-source
    properties:
      destinationName: person
      brokerURL: "tcp://redacted:port"
  sink:
    uri: "log:info"

Alternatively I tried to use:

configuration:
      - type: trait
        value: "logging.level=DEBUG"

However, it also does not cascade.

@orpiske
Copy link
Contributor Author

orpiske commented Jun 11, 2021

The expectation, here, is that the code would display the debug level messages ... but it does not seem to be the case.

@nicolaferraro nicolaferraro added this to the 1.5.0 milestone Jun 11, 2021
@orpiske orpiske changed the title Kamelets: configuration not does seem to cascade to the integration Kamelets: configuration does not seem to cascade to the integration Jun 11, 2021
@nicolaferraro nicolaferraro modified the milestones: 1.5.0, 1.6.0 Jul 5, 2021
@johnpoth
Copy link
Member

Wanted to do the same thing, as an alternative you can do:

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: jms-source-binding
spec:
  integration:
    traits:
      logging:
        configuration:
          level: DEBUG

thanks !

@squakez
Copy link
Contributor

squakez commented Aug 23, 2021

Yeah, I think that the new way of doing it will be via trait configuration. Before creating the log trait, we used to have a property to control the behavior, now we rely on trait configuration instead.

@orpiske
Copy link
Contributor Author

orpiske commented Aug 23, 2021

@squakez @johnpoth I guess we can probably consider this one outdated and then refer to the configuration via trait, since we have changed the way we are doing it. If you're OK with that, I'd say we can close this one.

@orpiske
Copy link
Contributor Author

orpiske commented Aug 23, 2021

Closing the issue as agreed, thanks!

@orpiske orpiske closed this as completed Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants