fixes #11121 - initialise websockets_encrypt after dependencies #2550
Conversation
This file contains 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
When settings.yaml (SETTINGS) is used to set websockets_encrypt to true, the key and cert need to be initialised first for its key/cert validation to pass.
|
LGTM, reproduced, tested, works on my system. Ping me once the patch for http://projects.theforeman.org/issues/11120 is ready so I can test that as well. |
|
Tests failed :( |
|
Not because of this though? |
|
Hmm [test] |
|
Merged as dc3ba8b, thank you! |
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.
When settings.yaml (SETTINGS) is used to set websockets_encrypt to true,
the key and cert need to be initialised first for its key/cert
validation to pass.