You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, deferInitPhase true or false needs to be decided by the application developer depending on whether she wants to pass different config values to the app at runtime. However, the CamelRuntime could potentially be made smart enough to decide based on the available config values. E.g. {{env:AWS_ACCESS_KEY}} is a clear indicator of a runtime value.
@gnodet noted in a call that this is not going to get resolved with Camel 3.0.0. We agreed to keep using the manual deferInitPhase in the mean time, eventually switching its default to true because it more likely to give what the users expect.
Currently,
deferInitPhase
true or false needs to be decided by the application developer depending on whether she wants to pass different config values to the app at runtime. However, the CamelRuntime could potentially be made smart enough to decide based on the available config values. E.g.{{env:AWS_ACCESS_KEY}}
is a clear indicator of a runtime value.cc @gnodet
The text was updated successfully, but these errors were encountered: