-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
lifecycle: Introduce a LifecycleConfig. See killbill/killbill#1911 #148
Conversation
We have a first use case to configure our lifecycle to decide whether system should exit when some plugins fail to start.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like tests need some additional Guice wiring.
@reshmabidikar Let's not forget to update our config docs.
if (exitOnError) { | ||
log.info("{} is set, so exiting..", EXIT_ON_LIFECYCLE_ERROR_PROPERTY); | ||
if (config.isServerExitOnLifecycleError()) { | ||
log.warn("Existing as system was configured to exist on lifecycle error "); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Existing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in ce72480
Looks like there are some test failures though. CI is red. |
Fixed in 0f4f895 |
We have a first use case to configure our lifecycle to decide whether system should exit when some plugins fail to start.