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

A kamelet should define which headers are supported as input and output #929

Open
davsclaus opened this issue May 16, 2022 · 4 comments
Open

Comments

@davsclaus
Copy link
Contributor

We should start to markup/specify which headers a sink and source kamelet can support as input and output.
For example the ftp sink kamelet should specify that the kamelet outputs ce-file as the filename of the FTP file.

The underlying FTP component also provides a set of headers
https://camel.apache.org/components/next/ftp-component.html#_message_headers

From Camel 3.17 then every component now list those in their documentation and metadata json file.

We need to consider whether we want Kamelets to expose these headers too, or we make a rule into kamelets that they output headers that the kamelet has declared.

And we also need to add into the kamelet spec how headers should be declared (ala options today).

@davsclaus
Copy link
Contributor Author

@lburgazzoli @oscerd another requirement for kamelets

@oscerd
Copy link
Contributor

oscerd commented May 17, 2022

We could leverage the Camel catalog from 3.17 ahead, but I guess we'll need to change the Kamelet structure to add some new fields. @lburgazzoli

@cjmamo
Copy link

cjmamo commented Aug 7, 2024

Is this supported now? I've seen Kamelets specifying the input and output headers like here:

dataTypes:
out:
default: json
headers:
CamelGoogleSheets.range:

@oscerd
Copy link
Contributor

oscerd commented Aug 7, 2024

Only the ones supporting data transformers. Not all

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