-
Notifications
You must be signed in to change notification settings - Fork 162
Sanitize web config only once #2286
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
Conversation
|
@micbar @ScharfViktor it seems I can't add labels here. |
really? Is this available after clicking by label?
label check is skipped for PR from fork. but you should be able add label |
|
@VicDeo You are onto sth here. But I am not really happy with your implementation, instead of using the |
dragonchaser
left a comment
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.
Please add explicit nil-checks instead of a bool workaround.
14a86ea to
6a271cd
Compare
|
@dragonchaser done |
|
|
Looks good, have approved CI-Run, waiting for it to turn green :) |
|
Thank you :) |




Description
Suture restarts failing service by executing the respective command. Cobra tries to execute PreRunE one more time that triggers config sanitization for already sanitized config.
Checking against an empty string triggers panic.
Related Issue
Motivation and Context
It makes the world a better place to live and fixes the panic if the port 9200 is already taken.
P.S. Execute
web.Execute(cfg.Web)command producesUsage:message in CLI on every restart on opencloud/pkg/runtime/service/service.go:264 so there are 5 such messages in console but that's completely different story.How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: