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

added shutdown quarkus config to env #117

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

pbhallam
Copy link
Collaborator

@pbhallam pbhallam commented Nov 4, 2022

No description provided.

Copy link
Collaborator

@wlingley wlingley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@jeesmon jeesmon left a 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",
Copy link

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",
},
{
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above

Copy link
Collaborator Author

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 .

Copy link

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)

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

Successfully merging this pull request may close these issues.

3 participants