-
Notifications
You must be signed in to change notification settings - Fork 345
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
Set env var with Kamel #606
Comments
I think the answer is no. What's the use case... Can you do an equivalent thing using config properties? |
Many times we need to extend JAVA_OPTIONS, or to set JAVA_MAX_MEM_RATIO, NO_PROXY arguments. Those arguments are treated by the (run-java.sh) https://github.com/fabric8io-images/run-java-sh/blob/master/fish-pepper/run-java-sh/fp-files/run-java.sh#L22 |
I think that's possible by using a configuration of type apiVersion: camel.apache.org/v1alpha1
kind: Integration
spec:
configuration:
- type: env
value: JAVA_OPTIONS=... I don't think you can add it using |
The reason why the env option is not exposes is that you can easily break things but if you can list the env var you need to tweak, we can create a trait so people won't risk to break camel-k |
Thanks @astefanutti & @lburgazzoli , i can set the env var by using:
But the deployment config is recreated after a new deployment with 'kamel run', hence we loose this env. The other approach proposed by @astefanutti , is to set this env directly in the integration spec:
With this one also we loose the env var after a new deployment with 'kamel run' |
Is it possible to set env var directly from the CLI Kamel ?
The text was updated successfully, but these errors were encountered: