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

Make CamelRuntime smart to decide deferInitPhase #96

Closed
ppalaga opened this issue Jul 25, 2019 · 3 comments
Closed

Make CamelRuntime smart to decide deferInitPhase #96

ppalaga opened this issue Jul 25, 2019 · 3 comments

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Jul 25, 2019

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

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 25, 2019

@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.

@ppalaga
Copy link
Contributor Author

ppalaga commented Aug 29, 2019

Change the default

@ppalaga
Copy link
Contributor Author

ppalaga commented Sep 3, 2019

See #172

@ppalaga ppalaga closed this as completed Sep 3, 2019
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

1 participant