Add a workaround to fix CAF OpenSSL options #2908
Merged
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.
In the
actor_system_config
, some settings are not like the others. While most modules read their options directly from thecontent
object, the SSL configuration is stored in member variables of the main config class. The CAF command line and config file parsers handle this correctly, but settings fromvast.yaml
files or those that are passed in as environment variables are injected through a different code path.This commit adds assignments to set the aforementioned class members explicitly.
I considered the alternative solution of translating non CAF-native option formats to native ones and let the
parse
function handle it, but that approach would be a large amount of work rather little benefit.