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

Lazily setup evaluation worker #195

Merged
merged 2 commits into from
Jan 20, 2017
Merged

Lazily setup evaluation worker #195

merged 2 commits into from
Jan 20, 2017

Conversation

0xdiba
Copy link
Contributor

@0xdiba 0xdiba commented Jan 20, 2017

Based on discussion for #193 .

// Try to continue with the locally hosted TLS configurations
err = json.Unmarshal([]byte(ServerSideTLSConfiguration), &sstls)
if err != nil {
log.Error(err)
log.Error("Could not load Server Side TLS configuration. Evaluation Worker not available")
//if we reach this stage, no TLS configs are loaded, so there is no need to have this worker available.
worker.RemoveWorker(workerName)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should just panic here. I can't think of a situation where I'd want to scanner to continue when loading the local conf has failed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think this is a valid scenario either, since fallback configurations are embedded in the code.
I will keep the RemoveWorker function in the worker just for consistency.

@jvehent jvehent merged commit 8874f71 into master Jan 20, 2017
@0xdiba 0xdiba deleted the lazily_setup_eval_worker branch January 20, 2017 14:22
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