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.
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
enhancement(deps)!: remove openssl legacy provider flag and update docs #18609
enhancement(deps)!: remove openssl legacy provider flag and update docs #18609
Changes from 8 commits
ea480d6
b5648e8
bdb9724
22d3558
f8dc18e
3479e86
1e8eb51
b5cdfe0
0f78f31
c2f3acd
ddcce64
5b6cf86
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
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.
The only concrete and relevant env variable is
OPENSSL_CONF
to specify an OpenSSL config file to use.I think mentioning "variables" and "particularly" is vague, misleading and confusing.
While outside of the scope of this PR, I still think Vector should document a complete example like I gave in the other closed PR. That should make it very clear how to use this functionality.
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.
Thanks, I wasn't sure if
OPENSSL_CONF
was the only relevant environment variable, hence the reason I was vague. I updated the wording using your suggestion 🙂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.
There is one more thing to consider maybe.
Vector's vendored OpenSSL library actually looks by default for
/usr/local/ssl/openssl.cnf
, which likely does not exist in most user's systems by default. TheOPENSSL_CONF
variable actually allows to override this to wherever you need.So, technically, if a user has an OpenSSL config in that path, Vector will pick it up automatically without needing
OPENSSL_CONF
. This behaviour can be suprising for them (maybe). Therefore, I'm not sure if this should be mentioned somewhere too.Perhaps a dedicated "Vector and SSL/TLS" documentation section is necessary to explain all these nuances?
Examples of using
OPENSSL_CONF
could go there for instance.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.
I agree that it would be useful to go into detail on this topic in the documentation. Given your expertise in the area, is this something you'd be willing to contribute? If not, I can open an issue to track this work.
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.
As I mentioned in the other PR where I investigated all of this, I'm more than happy to contribute documentation on the subject. As a starting point, can the Vector team suggest where in the documentation it would be suitable to open a new section/page for this topic?
At the moment it is hard for me to see where it would best fit in https://vector.dev/docs/ :(
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.
Thanks! I think this topic is worthy of its own page -
https://vector.dev/docs/reference/configuration/tls
seems like a good location. You can add this by creating a new markdown file similar to https://github.com/vectordotdev/vector/blob/master/website/content/en/docs/reference/configuration/unit-tests.mdThere 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.
Thanks for the pointer! Will work on it in the coming days.
I have one more ask, how can I quickly generate locally a render of the docs website?
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.
You should be able to run
make serve
in thewebsite
directory to spin up a local instance.