-
Notifications
You must be signed in to change notification settings - Fork 9
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
added shutdown quarkus config to env #117
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: pbhallam <[email protected]>
c37068e
to
e8f41bc
Compare
Signed-off-by: pbhallam <[email protected]>
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.
LGTM
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.
It's not a good idea to bleed implementation detail to operator as operator is agnostic of the underlying service. If this is a change needed for Quarkus I believe it should be in the respective service rather than hardcoding in operator.
@@ -141,6 +141,14 @@ func GetStowServiceEnv(cr *v1alpha1.DicomwebIngestionService, existing []corev1. | |||
Name: "EVENT_SOURCE", | |||
Value: fmt.Sprintf("%s.%s.svc.cluster.local", GetStowServiceName(cr), cr.Namespace), | |||
}, | |||
{ | |||
Name: "QUARKUS_SHUTDOWN_TIMEOUT", | |||
Value: "15S", |
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.
Why does operator needs to know about Quarkus. Operator should be unaware of implementation. Shouldn't this in application.properties of respective service (stow/wado)?
@@ -132,6 +132,14 @@ func GetWadoServiceEnv(cr *v1alpha1.DicomwebIngestionService, existing []corev1. | |||
Name: "QUERY_ENDPOINT", | |||
Value: eventProcessorServiceEndpoint + "/query", | |||
}, | |||
{ |
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.
Same as above
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.
I did not add this , this was there before my change .
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.
I was talking about L135-L142 (same comment as previous comment I added for stow_service.go)
No description provided.