config: fix "Insecure-security" constructor#2810
Merged
Conversation
MarcoPolo
approved these changes
May 22, 2024
| if err := cfg.addAutoNAT(bh); err != nil { | ||
| rh.Close() | ||
| app.Stop(context.Background()) | ||
| if cfg.Routing != nil { |
Collaborator
There was a problem hiding this comment.
This should be part of the stop lifecycle, no? Maybe we defer the fix until later
Member
Author
There was a problem hiding this comment.
wdym? We are not closing the host with the Stop lifecycle hook.
Collaborator
|
For folks skimming this PR. This is fixing the constructor for the "Insecure" security layer. It's not fixing an insecure construction of some other security layer. Folks should not be using the Insecure module except outside of testing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.