-
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
Issue when trying to configure env vars with annotations #2512
Comments
According the trait documentation, the trait is in charge to inject certain well known env variables, not to create any new one. The actual way to have it working would be to specify via
Perhaps you're suggesting to enhance the trait to include the possibility to declare the |
@squakez yes you are right, I got confused by the description of the trait as it says:
but then there's no reference to the key word in the table (it uses Properties) so I tough, that adding env vars would work. BTW, I think it would be valuable to be able to set env vars using a trait instead of the configuration section. @nicolaferraro @astefanutti @squakez what do you think ? |
I agree, we can probably move the |
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes #2512
Can someone add an example here? It really confuses about In my case, I have MYHOST and MYPORT in the environment variables and I tried |
If you're running directly from the |
@haifzhan, here is an example how to pass multiple environment variables with the environment trait:
In general, values of multiple occurrences of the same trait option are aggregated into an array, to emulate POSIX conventions, so the syntax is:
Or:
|
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes #2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
Moved the logic to process environment variable to trait. It will simplify setting via annotations Closes apache#2512
I have a KameletBinding with some traits configured using environment vars:
The generated integration fails with:
The text was updated successfully, but these errors were encountered: