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

Camel K 2.1 documentation still contains information on using local files for runtime resources despite it is no more supported #4853

Closed
apupier opened this issue Oct 24, 2023 · 5 comments
Assignees
Labels
area/documentation Documentation task

Comments

@apupier
Copy link
Contributor

apupier commented Oct 24, 2023

What happened?

While deploying with resource which are not config or secret file
the deployment is failing
with error:
Error: could not match config or secret configuration as file:/home/apupier/ws/single-file-without-extension-workspace/demo.camel.xml

The documentation is stating: The runtime resources are expected to be any resource type (text or binary content). https://camel.apache.org/camel-k/2.0.x/configuration/runtime-resources.html

Steps to reproduce

  1. Create a Camel K integration file
  2. Create a random file (which is not a config or secret file) like an xml file
  3. try to deploy the integration with a command like: kamel run Demo.java --resource=file:/path/to/the/file.xml

Relevant log output

`Error: could not match config or secret configuration as file:/home/apupier/ws/single-file-without-extension-workspace/demo.camel.xml`

Camel K version

2.1.0

@apupier apupier added the kind/bug Something isn't working label Oct 24, 2023
@gansheer
Copy link
Contributor

gansheer commented Oct 24, 2023

Hi,

The change has been made in Camel K 2.0 when deprecated kamel commands options have been removed : CAMEL K 2.0. If you want to provide a file you need to store it in a Configmap or Secret. This is why you no longer see any reference to "file:xxxx" in the documentation you are looking at.

@apupier
Copy link
Contributor Author

apupier commented Oct 24, 2023

I think the documentation needs a major update as it is still mentioning that the "most familiar way is to handle local file".
https://camel.apache.org/camel-k/next/configuration/runtime-resources.html

apupier added a commit to apupier/vscode-camelk that referenced this issue Oct 24, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@apupier apupier changed the title Camel K 2.1 is no more supporting resources which are not config or secret Camel K 2.1 documentation still contains information on using local files for runtime resources despite it is no more supported Oct 24, 2023
apupier added a commit to apupier/vscode-camelk that referenced this issue Oct 24, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@squakez squakez added area/documentation Documentation task and removed kind/bug Something isn't working labels Oct 24, 2023
apupier added a commit to apupier/vscode-camelk that referenced this issue Oct 24, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/vscode-camelk that referenced this issue Oct 24, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/vscode-camelk that referenced this issue Oct 24, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@gansheer
Copy link
Contributor

@squakez I will fix the doc.

apupier added a commit to apupier/vscode-camelk that referenced this issue Nov 2, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/vscode-camelk that referenced this issue Nov 2, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/vscode-camelk that referenced this issue Nov 6, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to camel-tooling/vscode-camelk that referenced this issue Nov 7, 2023
- remove command to deploy with a resource as it was provided only for
files and this feature has been deprecated in 2.0 and removed in 2.1
- the telemetry indicates that his feature was almost never used anyway
see apache/camel-k#4853 (comment)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@squakez squakez closed this as completed Nov 7, 2023
@MotaOcimar
Copy link
Contributor

Oh man. My routes use some json and velocity (.vm) files to format responses. What would be the easiest way for my Camel-K routes to reference these files?

@squakez
Copy link
Contributor

squakez commented Nov 24, 2023

Oh man. My routes use some json and velocity (.vm) files to format responses. What would be the easiest way for my Camel-K routes to reference these files?

Not sure to understand how this comment relates to this specific issue. Would you mind opening a separate issue with all the details about your request? thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Documentation task
Projects
None yet
Development

No branches or pull requests

4 participants